dprice
June 5, 2006, 15:13:19
Hello. We are building a product using the Enterprise TX control v12 .net. Our app builds and modifies documents based on information in a database. We are currently working on implementing undo. The TX control's built-in undo feature works very well for the text, however we also need to be able to keep track of what is on the undo stack in order to make corresponding changes to our data. So this is basically a wishlist for enhanced undo ability. It would be extremely helpful if a future version provided:
- UndoItemAdded/UndoItemRemoved events fired anytime the TX control adds or removes items from its undo stack. In our case this would allow us to maintain a list of undo events including our own custom items as well as those to be handled by the TX control. We could then catch undo requests and pass them through to the TX control or handle them ourselves as necessary.
- A way to either prevent an undo item from being created or alternatively a way to remove the last item added without actually executing that item. We frequently take action in code that we do not want to be undoable. For instance, we use empty fields to mark the location of blocks of text and we have to add and remove these fields programatically in various situations. It would be great if we could prevent these types of actions from being undoable without having to clear the entire undo stack with a call to ClearUndo().
- A count of undo items currently on the stack.
Thanks
- UndoItemAdded/UndoItemRemoved events fired anytime the TX control adds or removes items from its undo stack. In our case this would allow us to maintain a list of undo events including our own custom items as well as those to be handled by the TX control. We could then catch undo requests and pass them through to the TX control or handle them ourselves as necessary.
- A way to either prevent an undo item from being created or alternatively a way to remove the last item added without actually executing that item. We frequently take action in code that we do not want to be undoable. For instance, we use empty fields to mark the location of blocks of text and we have to add and remove these fields programatically in various situations. It would be great if we could prevent these types of actions from being undoable without having to clear the entire undo stack with a call to ClearUndo().
- A count of undo items currently on the stack.
Thanks