Node events
Every visual node supports<Node.Actions>; controls no longer need their own event attributes.
Action form:
Events
Function or Action
Each event uses one of them:Function: calls a widget function;Argumentsis optionalAction: uses the same action arguments as Button/Trigger- Event actions are included in the remote executable fingerprint. New or changed dangerous actions still require confirmation.
Relationship to built-in events
- Button
OnClickand inputOnChangestill work <Node.Actions>is an additional event layer; both run when declaredLoadedruns once per node instance and again after remounting
Limits
- Keyboard events require the node itself or a focusable descendant
MouseOver/MouseOutfire when entering or leaving the node; moving between descendants does not repeat themContextMenuprevents the default menu when an action exists- Events do not change layout; use a Function or Action for animation/property changes