Class TCircle2DNode

This item has no description. Showing description inherited from TAbstractGeometryNode.Proxy.

Converts this node to another node class that may be better supported.

Typically, converts some complex geometry node (like Extrusion or Teapot) into more common node like IndexedFaceSet or IndexedTriangleSet. TShape class wraps this method into a more comfortable interface, that is TShape methods simply automatically convert geometry nodes to their proxy versions if needed.

In the base TAbstractGeometryNode class, returns Nil indicating that no conversion is known.

The resulting node's Name (if the result is not Nil) must be equal to our Name.

Some Proxy implementations (especially for VRML 1.0) will have to create new State (TX3DGraphTraverseState) instance along with a new geometry node. You should do this by copying the State into a new TX3DGraphTraverseState instance, and modyfying the State reference. Simply speaking, do

State := TX3DGraphTraverseState.CreateCopy(State);

You should not just modify the fields of the provided State instance. (Reasoning: some proxy methods rely on getting the original State, e.g. with original MaterialBinding, not the transformed state, to work correctly.)

You can modify State variable only when returning non-nil geometry.

Source: scene/x3d/x3dnodes_standard_geometry2d.inc (line 57).

Create node fields and events.

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 35).

This item has no description. Showing description inherited from TX3DNode.ClassX3DType.

Node type name in VRML/X3D, for this class. Normal VRML/X3D node classes should override this to return something non-empty, and then X3DType automatically will return the same value.

Empty for classes that don't have a hardcoded VRML/X3D node name, like a special TX3DUnknownNode. Such special classes should override then X3DType to return actual non-empty name there.

You usually should call X3DType. The only use of this method is that it works on classes (it's "class function"), without needing at actual instance.

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 36).

Internal wrapper for property Radius. This wrapper API may change, we advise to access simpler Radius instead, if it is defined (TODO: for now, some field types do not have a simpler counterpart).

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 40).

Radius of the circle. If the RadiusY is non-zero (so we have ellipse, not a circle) then this is the radius along the X axis.

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 42).

Internal wrapper for property RadiusY. This wrapper API may change, we advise to access simpler RadiusY instead, if it is defined (TODO: for now, some field types do not have a simpler counterpart).

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 46).

Radius of the circle along the Y axis. Leave zero (default) to have a circle using Radius for both X and Y. Set to non-zero to have an ellipse, with Radius along X and this value along Y.

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 48).

Internal wrapper for property Slices. This wrapper API may change, we advise to access simpler Slices instead, if it is defined (TODO: for now, some field types do not have a simpler counterpart).

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 52).

How much to subdivide the circle. Larger values result in a shape that looks smoother (like a correct circle), but also mean that we need to render more triangles. The default value, 0 means to use the global DefaultTriangulationSlices parameter.

Source: scene/x3d/auto_generated_node_helpers/x3dnodes_circle2d.inc (line 54).