Documentation:VCurrent and vSelected: Difference between revisions

VCurrent and vSelected

Revision as of 06:52, 8 August 2023

This page was created by Hans.karlsen@mdriven.net on 2020-07-17. Last edited by Stephanie@mdriven.net on 2025-03-17.

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.

@@ 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. The variables are strongly typed to match your nestings and get the postfix name from the nesting.
+[[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.
-See this article for a fuller discussion on [https://blog.mdriven.net/cursored-or-full-tree/ how to cursor your ViewModel].
+The variables are strongly typed to match your nestings and get the postfix name from the nesting.
-See also [[How to use vCurrent and “self” correctly in viewmodels]]
+See this article for a fuller discussion on [[Cursored or Full Tree|how to cursor your ViewModel]].
+See also: [[How to use vCurrent and “self” correctly in viewmodels]]
 [[Category:View Model]]