Documentation:VCurrent and vSelected: Difference between revisions

VCurrent and vSelected

Revision as of 11:00, 17 July 2020

ViewModels create and maintain vCurrent_ and vSelected_ variables for each level of your viewmodel-nestings. The values are maintained by the framework to reflect what the user has focused/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 of how to cursor your viewmodel

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

Revision as of 10:58, 17 July 2020 (view source) Hans Karlsen (talk \| contribs) (Created page with "ViewModels create and maintain vCurrent_ and vSelected_ variables for each level of your viewmodel-nestings. The values are maintained by the framework to reflect what the use...") Tag: Visual edit		Revision as of 11:00, 17 July 2020 (view source) Hans Karlsen (talk \| contribs) No edit summary Tag: Visual edit Newer edit →
Line 1:		Line 1:
	ViewModels create and maintain vCurrent_ and vSelected_ variables for each level of your viewmodel-nestings. The values are maintained by the framework to reflect what the user has focused/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.		ViewModels create and maintain vCurrent_ and vSelected_ variables for each level of your viewmodel-nestings. The values are maintained by the framework to reflect what the user has focused/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 of [https://blog.mdriven.net/cursored-or-full-tree/ how to cursor your viewmodel]