Differences

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

--- 01_user_documentation:06_graph:05_derivation:02_transaction:01_log [2025/05/28 14:37] – sophiewachtel
+++ 01_user_documentation:06_graph:05_derivation:02_transaction:01_log [2025/11/03 05:41] (current) – gaetan
@@ Line 2: / Line 2: @@
 ====== Log ======
-The log maintains a record of all transactions applied to the project graph. This allows the following:
+Each operation on the project graph is performed through a [[:01_user_documentation:06_graph:05_derivation:02_transaction|transaction]]. These transactions are logged in a cache. It is possible to read through this log and apply the transaction in reverse enabling undo-ing the last modifications.
-==== Undo ====
+======  ======
-Logged transactions can be reversed, allowing the system to perform an "undo" operation on previous changes.
-==== Redo ====
+{{namespace>01_user_documentation:06_graph:05_derivation:02_transaction:01_log}}
-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.
-Once a new transaction is initiated (e.g. by):
-  * Running a new RGG function,
-  * Modifying an object through the attribute editor,
-  * Adding an object via the menu,
-the previous redo history is **discarded**. That means GroIMP does **not** support branching histories like version control systems.
-**Example of an unsupported sequence:**
-  - Undo → Apply new operation → Redo ❌
-After a new operation is applied following an undo, the redo path is no longer available.