Tree Control Events (Magic xpa 4.x)
You can use internal Tree control events to let the end user move, expand, and collapse nodes in the data tree.
The Tree control events are:
|
|
|
|
Collapse Node
|
Hides the parent's child records.
The information about triggering a node can be provided through arguments passed by the Expand Node and Collapse Node events. When selecting either the Expand Node or Collapse Node events, Magic xpa prompts you with a confirmation message about creating the Tree Node Value and Tree Node Level virtual variables.
When the Expand Node or Collapse Node events are triggered, the corresponding virtual variable for the user-defined handler is updated with tree node values related to the triggered event. The first variable is updated with the Tree Node Value. The second variable is updated with the Tree Node Level.
Raising the Expand Node and Collapse Node events outside the scope of the Tree control will not update the Tree Node Value and Tree Node Level fields.
Arguments passed by a Raise Event operation for the Expand Node and Collapse Node events are set in the handler's virtual fields.
|
Minus Left
|
TR07, RTR07
|
Create Child
|
Creates a child node representing a record.
|
|
TR20, RTR20
|
Edit Node
|
Enables editing of the current node descriptions. Triggering the Edit Node lets you edit a node that the engine is parked on. Click the mouse button to select the node. Click the mouse button a second time to trigger the event.
|
F2
|
TR19, RTR19
|
Expand Node
|
Displays a parent's child record.
The information about triggering a node can be provided through arguments passed by the Expand Node and Collapse Node events. When selecting either the Expand Node or Collapse Node events, Magic xpa prompts you with a confirmation message about creating the Tree Node Value and Tree Node Level virtual variables.
When the Expand Node or Collapse Node events are triggered, the corresponding virtual variable for the user-defined handler is updated with tree node values related to the triggered event. The first variable is updated with the Tree Node Level. The second variable is updated with the Tree Node Value.
Raising the Expand Node and Collapse Node events outside the scope of the Tree control will not update the Tree Node Level and Tree Node Value fields.
Arguments passed by a Raise Event operation for the Expand Node and Collapse Node events are set in the handlers' virtual fields.
|
Plus Right
|
TR07, RTR07
|
Move to Parent
|
Moves the focus to a parent node.
|
|
TR18, RTR18
|
To First Child
|
Moves the focus to the first child node.
|
|
TR18, RTR18
|
To Next Sibling
|
Moves the focus to the next sibling node.
|
|
TR18, RTR18
|
To Previous Sibling
|
Moves the focus to the previous sibling node.
|
|
TR18, RTR18
|
The information about triggering a node can be provided through arguments passed by the Expand Node and Collapse Node events. When selecting either the Expand Node or Collapse Node events, Magic xpa prompts you with a confirmation message about creating the Tree Node Level and Tree Node Value virtual variables.
When the Expand Node or Collapse Node events are triggered, the corresponding virtual variable for the user-defined handler is updated with tree node values related to the triggered event. The first variable is updated with the Tree Node Level. The second variable is updated with the Tree Node Value.
Raising the Expand Node and Collapse Node events outside the scope of the Tree control will not update the Tree Node Value and Tree Node Level fields.
Arguments passed by a Raise Event operation for the Expand Node and Collapse Node events are set in the handler’s virtual fields after the first two variables.
The Edit Node Studio and Runtime events let you edit the Tree control node descriptions in Development or Runtime mode. Triggering the Edit Node Runtime event only lets you edit a mode that is parked upon. Click the left mouse button to select the node. Click the left mouse button a second time to trigger the event.
How Do I Explicitly Expand/Collapse Tree Nodes at Runtime?
How Do I Respond to any Expand/Collapse Activity Performed on the Tree Control By the End User?