SnapSensor
SnapSensors snap into SnapIns. Think of them as a filter between e.g. a SpaceSensor and the Transformation it controls. The SpaceSensor is routed through the SnapSensor into the target field. If the SnapSensor is close to a compatible SnapIn, it will adjust the incoming transformation to match the SnapIn's constraints. The typical route connections: sender.matrix_changed TO snapSensor.set_matrix snapSensor.matrix_changed TO receiver.set_matrix sender.isActive TO snapSensor.set_isActive snapSensor.matrixOffset_changed TO sender.set_matrixOffset
Inheritance
Code
XML encoding
<SnapSensor matrix='identity' translation='0 0 0' rotation='0 0 1 0' idList='default' sensingRadius='10' locationOffset='identity' locationTranslation='0 0 0' locationRotation='0 0 0 1' visibleSize='1.0' description='' enabled='TRUE' logFeature='' />
Classic encoding
SnapSensor { matrix identity translation 0 0 0 rotation 0 0 1 0 idList ["default"] sensingRadius 10 locationOffset identity locationTranslation 0 0 0 locationRotation 0 0 0 1 visibleSize 1.0 description "" enabled TRUE logFeature [""] }
Interface
Filter: X3D only | Avalon only | All
id | Name | DataType | PartType | Default | ValueType | Description |
---|---|---|---|---|---|---|
![]() |
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 | |
![]() |
metadata | SFNode | inputOutput | MetadataObject | container for payload metadata inside MetadataSet element |