Class TAbstractBindableNode

Automatically generated node properties.

Do not edit this file manually! To add new properties: - add them to the text files in tools/internal/x3d-nodes-to-pascal/nodes-specification/ , - and regenerate include files by running x3d-nodes-to-pascal

"Bound" node is the node currently used, for example the "bound" background determines the current background look. Setting this to True means that the node becomes the current node of the given type in the scene.

In every scene (TCastleScene), there are four "stacks" of bindable nodes:

1. Viewpoints determine the camera position/orientation, field of view, orthographic/perspective projection etc.

2. NavigationInfo determines the current navigation type, avatar size etc.

3. Background determines the dispayed background (like a skybox or a simple solid color).

4. Fog determines the current fog.

The top-most node of each stack is called "bound". If the scene is set as TCastleRootTransform.MainScene, then the "bound" node determines the camera, background or fog settings.

Setting this property to True sends an X3D event "set_bind := true". This adds the node to the stack, and makes sure it is at the top. Setting this to False pops the node from the stack. See the X3D specification about the "bindable nodes" foe details: http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/core.html#BindableChildrenNodes

Transformation of this bindable node.

Bound nodes cannot be instantiated multiple number of times (this would make simple event like "set_bind" not possible, as it would not be known in what coordinate space the node is bound), so it's perfectly safe and comfortable to just keep their transformation here, a their property.

It is gathered during traversing. Last BeforeTraverse call for this node sets Transform properties. By default, these represent identity transformation.

Note that using TransformScale for bindable nodes like fog is a little simplification. Theoretically, the scale can be non-uniform, and around an arbitrary axis. So to apply e.g. fog, we should transform the 3D world back into local fog coordinate system, and calculate the distances there. Instead right now we do the opposite: transform stuff like fog VisibilityRange by TransformScale, and calculate distances in world coordinate system. This is a simplification, but in practice it's perfect (who uses non-uniform fog scale?) and it can be expressed for renderers (OpenGL) without any problems.