no description available, TX3DSingleField description follows
no description available, TX3DField description follows
Base class for all VRML/X3D fields.
Common notes for all descendants: most of them expose field or property "Value", this is (surprise, surprise!) the value of the field. Many of them also expose DefaultValue and DefaultValueExists fields/properties, these should be the default VRML value for this field. You can even change DefaultValue after the object is created.
Most of descendants include constructor that initializes both DefaultValue and Value to the same thing, as this is what you usually want.
Some notes about Assign method (inherited from TPersistent and overridied appropriately in TX3DField descendants):
There are some exceptions, but usually assignment is possible only when source and destination field classes are equal.
Assignment (by Assign, inherited from TPersistent) tries to copy everything: name (with alternative names), default value, IsClauseNames, ValueFromIsClause, Exposed, and of course current value.
If True then when trying to set Value to something < 0, we'll negate it (in other words, we'll keep Value >= 0 always). This is nice e.g. for Sphere.FdRadius field — some incorrect VRML specify negative sphere radius.
Value represents an angle. When reading from X3D 3.3 file, we will make sure it's expressed in radians, honoring optional "UNIT angle ..." declaration in X3D file.