LoadSensor
LoadSensor generates events as watchList child nodes are either loaded or fail to load. Changing watchlist child nodes restarts the LoadSensor. Hint: use multiple LoadSensor nodes to track multiple loading nodes individually. Hint: Background is not sensed due to multiple-image ambiguity. Warning: watchList child nodes are not rendered, so normally USE copies of other nodes to sense load status. Hint: use Inline 'load' field to prompt or defer loading. Warning: new X3D node, not supported in VRML 97.
Inheritance
Code
XML encoding
<LoadSensor timeOut='0' triggerName='Timer' description='' enabled='TRUE' logFeature='' />
Classic encoding
LoadSensor { timeOut 0 triggerName "Timer" description "" enabled TRUE logFeature [""] }
Interface
Filter: X3D only | Avalon only | All
id | Name | DataType | PartType | Default | ValueType | Description |
---|---|---|---|---|---|---|
triggerName | SFString | initializeOnly | Timer | 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-eventOut to the triggerSlot-eventInput Slot. | ||
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 |