|
|
Undo and redo now behave as one history per diagram.
Each diagram keeps its own sequence of element actions with the model changes woven into it. Undo in a diagram follows that sequence. When it reaches a model change, the model is rolled back and every open diagram reflects it, while each diagram's own element actions stay exactly where they were. A model change that another diagram has already undone is simply stepped over, so undo never reverses something twice or reverses the wrong thing.
Changed for the user:
- Undo always reverses the last thing done in that diagram, including immediately after a save.
- Redo mirrors undo completely: a re-added element returns with its original position, size and automatic-size setting, and moved containers and relation points are restored.
- Redo of a model change stays reachable from a diagram, no matter how many element actions were performed since.
- Saving no longer clears the undo history, and the option that controlled this has been removed. A save is a checkpoint on disk, not the end of an editing session, so you can undo straight past it.
- With the split conceptual view enabled, Undo now acts on the diagram, and the Notes text is only affected while the Notes tab itself is in front.
- Undo and Redo are unavailable on a read-only diagram and while the model is locked, instead of appearing to work.
- Undoing the placement of an element also updates the model's record of what the diagram contains, so it no longer reappears on reload.
- Changes that come from the model, such as a synchronisation after someone else's edit, are no longer recorded as if you had placed or removed the element yourself.
Known limitation: if you undo a model change and then a change made elsewhere takes its place before you do anything in the diagram, that new change cannot be undone from this diagram. It remains undoable from the diagram where it was made and from the model views. |
