| 12 | | Grouping is also important, because changing one property may cascade and change 12 others. This task needs to track this and make sure it is undoable. |
| 13 | | |
| 14 | | This task also needs to document the undo manager so that others use it properly. |
| 15 | | |
| 16 | | Also consider the need to merge change sets. This would be applicable in, for example, a collaborative environment. Whatever sets come out of the grouping requirement, determine if those change sets are able to be merged, or if this is an impossible task for now. |
| | 12 | The goal of this task is to provide an end user interface to the change manager. Add a user interface via the Edit menu for Undo and Redo. I don't think we should expose skipping, as that would be confusing to the user. |
| 20 | | * Evaluate the current undo mechanism in PRO_LIB |
| 21 | | * Add the ability to undo/redo auto property changes |
| 22 | | * Add the ability to group changes |
| 23 | | * Evaluate the ability to merge change sets |
| | 16 | * Add menu items to the edit menu that tracks the state of the change manager |
| | 17 | * Undo works down the stack |
| | 18 | * Redo works up the stack |
| | 19 | * Add key commands (control-z, control-shift-z for redo) to the menu items |
| | 20 | * Disable the menu items if you are at the proper end of the stack |
