Documentation:VCurrent and vSelected: Difference between revisions

VCurrent and vSelected

Revision as of 06:03, 2 October 2023

ViewModels create and maintain vCurrent_ and vSelected_ variables for each level of your ViewModel-nestings.

The values maintained by the Framework reflect what the user has focused on/clicked last (vCurrent_), and when you allow multi-select in grids, the vSelected_ collection is maintained.

The variables are strongly typed to match your nestings and get the postfix name from the nesting.

See this article for a fuller discussion on how to cursor your ViewModel.

This page was edited 70 days ago on 03/04/2024. What links here

@@ Line 1: / Line 1: @@
-[[ViewModel|ViewModels]] create and maintain vCurrent_ and vSelected_ variables for each level of your ViewModel-nestings. The values maintained by the Framework reflect what the user has focused on/clicked last (vCurrent_), and when you allow multi-select in grids, the vSelected_ collection is maintained.
+[[ViewModel|ViewModels]] create and maintain vCurrent_ and vSelected_ variables for each level of your ViewModel-nestings.
+The values maintained by the Framework reflect what the user has focused on/clicked last (vCurrent_), and when you allow multi-select in grids, the vSelected_ collection is maintained.
 The variables are strongly typed to match your nestings and get the postfix name from the nesting.