Node scope

All nodes are created during the script parsing activity. All nodes must have a globally unique name to use as an address. Both nodes whose name is automatically assigned by the scripting parser (the ones that do not override the name field) and the nodes named directly by the script developer must have a globally unique name.

Regardless of where a node is defined, it can always be referenced in another script file. You can always link to a field of a node that is defined inside another context or another file.

A node is always loaded and alive in application memory.

A node can be:

• Defined in a script file that differs from the main script.

• Contained inside a non-active context.

• Linked to an object inside an inactive MWX.

The node definition and connection order is not relevant. You do not need to define a node before referencing it. It's enough to have its declaration somewhere in the scripts. The only exception is the special patch node. This behavior helps make project script file organization more flexible.

Structure

Script developers can use whatever script files structure they prefer. For example, the main file can contain links to context-related files or templates. The connections can be put into separate scripts to increase code readability. Developers can leverage this flexibility to structure and manage complex scripts in a clear and organized way.

For full list, see List of nodes.