3.9. Use Undo Redo

Use Undo/Redo

One-liner: when available, choose Edit → Undo or Edit → Redo from the Menu .

Explanation:

MAIDENS takes a full snapshot of the current document after each revertible operation.

Using Undo and Redo, you practically navigate back and forth through these snapshots. Also, one snapshot is automatically taken after a project is loaded or created. This way there will always be a snapshot in the Undo/Redo history that stores the current state of affairs.

The following operations trigger snaphots, and therefore are revertible using Undo:

• adding or deleting any type of node in the project hierarchy. This covers all create and delete operations;
• changing any node property using the Editor;
• cutting or pasting, which is regarded as a single atomic operation, despite the fact that it internally involves subjacent add/delete operations;
• applying a macro, also regarded as a single operation;
• generating content using any of the available generators (an atomic operation as well).

Nota bene: MAIDENS has a hard limit of 20 project snapshots that can be stored, which gives you at most 20 undo steps. When this limit is hit, the oldest entry in the snapshots history will be discarded to make room for a new one.

The menu items display dynamic headers based on operation availability and type. See the Edit → Undo and Edit → Redo sections in the Menu UI article for more insight.

Nota bene: The snapshot history is linear, and cannot do any branching. That is why, if you change your project after undoing something, the more recent snapshots in the history are permanently deleted — in other words, you loose the ability of redoing what was undone.