MDrivenStart ViewModelActions
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
ViewModelActions have similar functionality as '''[[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, you give what it is currently focused on in the view in 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 '''[[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 [[vCurrent and vSelected]].
Read more on [[vCurrent and vSelected]].

Latest revision as of 06:54, 24 July 2023

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.

Read more on vCurrent and vSelected.

Back One Back to Start Chat Updated!

This page was edited more than 9 months ago on 07/24/2023. What links here