BboxSensor2D
This sensor can be used to monitor the bounding-boxes of any node in the scene-graph. It sends bbox_changed events if the global bboxes of the node changed. Every bbox is defined by a min/ max pair in screen coordinates. Since the system is a multiparent graph a node can have more than one global bbox and therefor the bbox_changed outslot can send more than one min/ max pair.
Inheritance
Code
XML encoding
<BboxSensor2D triggerName='Synchronize' description='' enabled='TRUE' logFeature='' />
Classic encoding
BboxSensor2D {
triggerName "Synchronize"
description ""
enabled TRUE
logFeature [""]
}
Interface
Filter: X3D only | Avalon only | All
| id | Name | DataType | PartType | Default | ValueType | Description |
|---|---|---|---|---|---|---|
 |
bbox_changed | MFVec2f | outputOnly | Outslot that sends all global bbox pairs in screen coordinates (min/ max) on change. | ||
 |
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 |