libcoral/coral-calcium — Issue #5: UndoManager's redo stack is not being reset after a new change
Author: tbastos
Created: 2011-11-07 08:40:18+00:00
State: open
Labels: problem

- Correct behavior for the UndoManager would be to clear the redo stack once a new change (i.e. any changeset that's not an undo) is made.
- Add a test case to the test suite.

How to replicate the problem:
- Change field from state A to state B.
- Undo change.
- Change field from state B to state C.
- Redo change. Field returns to state B, the user's change is lost.

Reported by @xvaldetaro