Documentation:ViewModel actions: Difference between revisions

ViewModel actions

Revision as of 05:48, 27 June 2024

ViewModelActions have similar functionality as Class actions, but they act on ONE view rather than on the objects of a class - so you will find no "self" here. Instead, give what it is currently focused on in the view as variables starting with vCurrent_ . When the user has selected multiple items in grids, you will find them in vSelected_ collections for the corresponding View Model nesting.

Revision as of 05:47, 27 June 2024 (view source) Stephanie Namugambe (talk \| contribs) No edit summary Tag: Visual edit ← Older edit		Revision as of 05:48, 27 June 2024 (view source) Stephanie Namugambe (talk \| contribs) No edit summary Tag: Visual edit Newer edit →
Line 3:		Line 3:
	ViewModelActions have similar functionality as [[/wiki.mdriven.net/MDrivenStart ClassActions\|Class actions]], but they act on ONE view rather than on the objects of a class - so you will find no "self" here. Instead, give what it is currently focused on in the view as variables starting with <code>vCurrent_</code> . When the user has selected multiple items in grids, you will find them in <code>vSelected_</code> collections for the corresponding View Model nesting.		ViewModelActions have similar functionality as [[/wiki.mdriven.net/MDrivenStart ClassActions\|Class actions]], but they act on ONE view rather than on the objects of a class - so you will find no "self" here. Instead, give what it is currently focused on in the view as variables starting with <code>vCurrent_</code> . When the user has selected multiple items in grids, you will find them in <code>vSelected_</code> collections for the corresponding View Model nesting.

	Read more on [[~~/wiki.mdriven.net/~~VCurrent and vSelected\|vCurrent and vSelected]].{{Edited\|July\|12\|2024}}		Read more on [[Documentation:VCurrent and vSelected\|vCurrent and vSelected]].{{Edited\|July\|12\|2024}}