TreeSensor
Abstract base node for all sensors which monitor the state of a subgraph or node-tree. Those Sensors can be used to monitor the tree of the parent node and therefore can be utilized with any node which can hold childs (e.g. Group, Transform)
Inheritance
Code
XML encoding
<TreeSensor triggerName='Synchronize' description='' enabled='TRUE' logFeature='' />
Classic encoding
TreeSensor {
triggerName "Synchronize"
description ""
enabled TRUE
logFeature [""]
}
Interface
Filter: X3D only | Avalon only | All
| id | Name | DataType | PartType | Default | ValueType | Description |
|---|---|---|---|---|---|---|
 |
triggerName | SFString | initializeOnly | Synchronize | name of the dynamic context-slot which is used by the run-time environment (e.g. Jobs) to trigger the node. Life-Nodes will automatically connect the context-eventOutut to the triggerSlot-eventInput Slot. | |
|
description | SFString | inputOutput | Text description to comment the sensor task. Can be used in run-time systems to give usefull feedback to the user and developer | ||
 |
enabled | SFBool | inputOutput | TRUE | Enables/disables the sensor node. | |
|
isActive | SFBool | outputOnly | FALSE | isActive true/false events are sent when the sensor gets active | |
 |
triggerSlot | SFTime | inputOnly | slot which is used internally to connect a dynamic context-slot which name is set by the triggerName value. Its used automatically to install run-time environment trigger. | ||
 |
logFeature | MFString | inputOutput | state, child, parent, route, eventIn, eventOut | controls the logging of changes, state: log state changes (e.g. live), child: log child add/remove, parent: log parent add/remove, route: log route add/remove; eventIn: log receiving of events, eventOut: log sending of events: guiView, runtime system should create node-view, guiEdit: runtime system should create node-editeverything: log everything | |
 |
metadata | SFNode | inputOutput | MetadataObject | container for payload metadata inside MetadataSet element |