Designer guide
Toolbar history and dirty stateUndo, redo, and saving — Visual Service Design
History records user actions, not every reactive update. Property edits and moves use compact before/after changes; structural edits retain a snapshot fallback.
When to use
Use this page while editing or reviewing the graph in the designer.
Behavior
- Use toolbar Undo and Redo for property edits, additions, removals, connections, and component changes. Compound model actions, such as inserting a Split and rewiring its consumers, form one history entry.
- One drag creates one move action, even for a component or a multi-node selection; pointer updates do not become hundreds of history entries. Property changes are restored directly, while structural snapshots reconstruct the model and reconcile selections.
- The Save button is enabled only when the project is dirty. Saving records the current model as the saved baseline.
- The project menu in the application bar contains New, Load, Save, Save As, Generate project, and Download Python project. Loading another project with unsaved changes opens a Save, Discard, or Cancel guard.
- The top toolbar also exposes sign-in or sign-out and language controls; these do not change graph semantics.
Configuration example
Open the designer and select Graph.