Node Editor

Overview

The Node Editor provides a visual environment for working with the node-based programming systems in Grid Studio.

Within this view, users can create, edit, and inspect node graphs that define logic and data processing within a project.

The Node Editor acts as a shared editor used by multiple systems and allows node graphs to be visually designed and inspected.


Supported Systems

The Node Editor can display and edit two different node-based systems:

  • Modifier – used for real-time data processing and value manipulation

  • Workflow – used for event-driven logic and system control

Depending on the selected object or editor context, the Node Editor automatically switches to the appropriate system.

This allows both node systems to be edited within the same visual environment.


Dynamic Behavior

The Node Editor supports dynamic view behavior.

When an object that contains a node graph is selected, the Node Editor automatically loads the corresponding graph.

Like other dynamic views, the Node Editor can also be locked to a specific object, preventing it from updating when the global selection changes.


Multiple Node Editors

It is possible to open multiple Node Editor views within the workspace.

Each Node Editor operates independently and can display the node graph of different objects. This allows users to work with multiple node systems simultaneously.

For example, one Node Editor can display the Workflow of an object while another shows its Modifier, or different node graphs from separate objects.

Because the Node Editor is a dynamic view, each editor normally updates when the global selection changes. However, a Node Editor can also be locked to a specific object, allowing users to keep a graph visible while navigating to other objects in the project.

This setup can be useful when comparing logic, debugging node graphs, or transferring ideas between different systems.


Editor Header

At the top left of the Node Editor window, the header indicates which object is currently being edited.

This header also provides quick access to create or switch between node systems associated with the selected object.

Create System

If the object does not yet contain a node system, a Create button is displayed.

This allows users to create either:

  • a Workflow

  • a Modifier

directly from the Node Editor.

Object Selection

The object name displayed in the Node Editor header indicates which object is currently being edited.

Clicking on the object name opens a list of all project objects that contain a Workflow or Modifier.

This allows users to quickly switch between different node graphs without needing to select the object in the Project Tree first.

Selecting an object from this list will immediately load its corresponding node graph in the Node Editor.

This feature provides a fast way to navigate between node-based systems across a project.

Existing Systems

If the selected object already contains a node system, the header displays an icon representing the available system.

For example:

  • a Workflow icon when the object has a workflow

  • a Modifier icon when the object has a modifier

Switching Between Systems

If an object contains both a Workflow and a Modifier, the Node Editor allows users to switch between them directly from the header.

Clicking the corresponding icon loads the selected node graph in the editor.

This makes it possible to work with both systems without leaving the Node Editor view.


Special Selection Behavior

The Node Editor has slightly different selection behavior compared to other dynamic views because it supports editing graphs from different object types.

Selecting elements inside the Node Editor may update the global selection differently than selecting objects in other views.

More details about this behavior can be found in the Navigation section.


Purpose

The Node Editor provides the primary visual interface for designing and inspecting node-based logic in Grid Studio.

It enables users to build complex processing pipelines and automation systems using a visual node graph.


  • Workflow – Event-driven logic and system control

  • Modifier – Real-time data processing and value manipulation

  • Navigation – Selection and navigation behavior in the editor

Last updated