The list of changes collected during a transaction. The changes are stored in order of occurrence. You should not modify this list.
Details about the operation, for example: "Update" may be the display name for an edit operation that updates features.
The TransactionManager for this transaction.
The parent transaction containing this instance. The value will be null for top-level transactions.
User state object
The status of this transaction (e.g. None, Committed, Aborted)
Records an undo operation as part of this transaction. Transactions are undone (or redone) as a single atomic operation.
The undo operation to record within this transaction.
Commits the undo operation of this UndoTransaction
Returns a boolean value indicating whether any undo operations have been recorded for this transaction.
Whether this transaction was aborted (rolled back)
Whether this transaction was committed.
Whether we can add more undo operations to the list of changes for this transaction.
Whether this is a top-level transaction. Top-level transactions have no parent and thus are not nested.
Invokes the performRedo method for all contained Undoables in the order in which they were added.
Invokes the performUndo method for all contained Undoables in the reverse of the order in which they were added.
Rolls back (aborts) the transaction and calls the undo operations to recover the state before the UndoTransaction was created.
An UndoTransaction is used to group one or more undo operations into a single item in the undo/redo history. Multiple undo operations can be added to a transaction's private stack. When a transaction is committed, the whole transaction will be pushed to the top of the undo stack of the UndoManager. Rolling back a transaction will invoke all contained undo operations, but they won't be pushed to the undo history of the UndoManager.