Class TAbstractScriptNode

This item has no description.

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

Constructor. Initializes various properties:

• Name, BaseUrl are initialized from given parameters.

• The Fields, Events lists are filled in every descendant, to have all the fields/events defined by the specification.

• DefaultContainerField, and other node-specific stuff, is filled in descendants. This is actually implemented in CreateNode, that is called at the end of this constructor.

This item has no description.

Clear the memory when the last events were generated from this script.

TCasScriptVRMLValuesList.ResetLastEventTimes

See also

TX3DRoute.ResetLastEventTime

Clear the memory when the last event passed through this route.

Create node fields and events.

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.

This item has no description.

This item has no description.

Initialize / shutdown of the script. Read this to know current script state, write this is to actually initialize/shutdown if needed.

Note that the script node doesn't initialize itself at any point. Reason: there's no comfortable moment to do this: 1. in constructor some routes and such are not initialized yet, and we should initialize script after whole VRML graph is loaded. 2. tricks with BeforeTraverse, like used for TInlineNode, are not Ok, since scripts must work even when they are in the inactive part of VRML graph.

If you want scripts to work, you have to initialize them yourself. If you use TCastleSceneCore, this will be done for you automatically when you change TCastleSceneCore.ProcessEvents, so it's not a problem in practice.

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