User Tools

Site Tools


01_user_documentation:06_graph:05_derivation:02_transaction:01_log:02_redo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
01_user_documentation:06_graph:05_derivation:02_transaction:01_log:02_redo [2025/07/04 15:01] gaetan01_user_documentation:06_graph:05_derivation:02_transaction:01_log:02_redo [2025/11/03 05:44] (current) gaetan
Line 2: Line 2:
 ====== Redo ====== ====== Redo ======
  
-The log also keeps track of transactions that have been undone, enabling you to "redo" them if needed.+The log also keeps track of transactions that have been undone, enabling you to "redo" them if needed. Undo and redo operations can be performed in sequence (a "chain"), but once a new command is executed, the chain of possible redos is cleared. Thus, it is possible to re apply the transactions previously "undone". Yet, one a new transaction is performed (running a new RGG function, applying a modification through the attribute editor, adding an object through the menu, ...) the chain of transaction do not lead to the "redo" anymore. Thus, it is not possible to "undo" > apply new > "redo"
  
 ======  ====== ======  ======
- 
- 
-Undo and redo operations can be performed in sequence (a "chain"), but once a new command is executed, the chain of possible redos is cleared. 
- 
  
 Once a new transaction is initiated (e.g. by): Once a new transaction is initiated (e.g. by):
  
-  * Running a new RGG function,+  * Running an RGG function,
   * Modifying an object through the attribute editor,   * Modifying an object through the attribute editor,
   * Adding an object via the menu,   * Adding an object via the menu,
01_user_documentation/06_graph/05_derivation/02_transaction/01_log/02_redo.1751634110.txt.gz · Last modified: 2025/07/04 15:01 by gaetan