Documentation:VCurrent and vSelected: Difference between revisions

VCurrent and vSelected

Revision as of 05:23, 6 February 2024

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 71 days ago on 03/04/2024. What links here

Revision as of 21:13, 20 December 2023 (view source) Wikiadmin (talk \| contribs) m ((username removed) (log details removed): Moving to Documentation namespace) ← Older edit		Revision as of 05:23, 6 February 2024 (view source) Stephanie Namugambe (talk \| contribs) No edit summary Tag: Visual edit Newer edit →
Line 1:		Line 1:
	[[ViewModel\|ViewModels]] create and maintain vCurrent_ and vSelected_ variables for each level of your ViewModel-nestings.		[[Training: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 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.