MDrivenStart ViewModelActions
No edit summary
Tags: Reverted Visual edit
No edit summary
Tags: Reverted Visual edit
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]].

Revision as of 06:38, 24 July 2023

This page was created by Hans.karlsen@mdriven.net on 2020-07-10. Last edited by Stephanie@mdriven.net on 2025-01-31.

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!

MDriven Chat

How would you like to chat today?

Setting up your conversation…

This may take a few moments