IUndoStack interface Core

Grid-wide undo/redo as a CONTRACT, not a concrete table type.

This is the pattern every serious grid and editor converges on: ONE history service holding inverse-operation entries (command pattern), fed at the model's commit choke point, with batch brackets so a composite gesture undoes as a single step. A template that owns mutations (a table, a timeline drag, a chart edit) implements this, and the grid wiring, the toolbar commands and the shortcut all talk to the contract.

IUndoStack.Record is the seam for STRUCTURAL changes that do not travel through a cell write (move an activity, split an interval, insert a row): the caller hands the two closures, the implementation owns ordering, capping and the redo-invalidation rule (a new entry clears the redo side). Implementations must ignore a IUndoStack.Record that happens while a replay is running — the undo of an undo is the redo entry it came from, not a fresh recording. Batch brackets stay on ISlotModel.BeginEditBatch/ISlotModel.EndEditBatch: they scope CELL commits and recordings alike, so a drag that writes two cells and records one structural entry still undoes as one step.

public interface IUndoStack

Namespace

ArionUI.Core

Package

ArionUI.Core · dotnet add package ArionUI.Core --prerelease

Properties

bool CanRedo { get; }

bool CanUndo { get; }

int RedoDepth { get; }

int UndoDepth { get; }

Methods

void Clear();

void Record(Action undo, Action redo);

bool Redo();

bool Undo();

Events

event Action? HistoryChanged;