ViewpointGroup
ViewpointGroup is used to control display of viewpoints on the viewpoint list. Use of ViewpointGroup allows a viewpoint list to have a tree structure, similar to a bookmark list.
Inheritance
Code
XML encoding
<ViewpointGroup description='' displayed='TRUE' center='0 0 0' size='0 0 0' retainUserOffsets='FALSE' logFeature='' />
Classic encoding
ViewpointGroup { description "" displayed TRUE center 0 0 0 size 0 0 0 retainUserOffsets FALSE logFeature [""] }
Interface
Filter: X3D only | Avalon only | All
id | Name | DataType | PartType | Default | ValueType | Description |
---|---|---|---|---|---|---|
children | MFNode | inputOutput | SceneBaseNode | The children field is a sequence of Viewpoint or ViewpointGroup nodes. | ||
description | SFString | inputOutput | The description field provides a simple description or navigation hint to be displayed for this ViewpointGroup. | |||
displayed | SFBool | inputOutput | TRUE | The displayed field determines whether this ViewpointGroup is displayed in the current viewpoint list. | ||
center | SFVec3f | inputOutput | 0 0 0 | (-∞, ∞) | The center field provides a position offset from origin of local coordinate system | |
size | SFVec3f | inputOutput | 0 0 0 | (-∞, ∞) | The size field provides the size of a proximity box within which the ViewpointGroup is usable and displayed on the viewpoint list. A size field of 0 0 0 specifies that the ViewpointGroup is always usable and displayed. | |
retainUserOffsets | SFBool | inputOutput | FALSE | The retainUserOffsets field specifies whether the user is returned to the originally defined viewpoint position/orientation after local navigation | ||
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 |