On Jan 9, 2008 8:58 AM, Frank Schönheit - Sun Microsystems Germany <[EMAIL PROTECTED]> wrote:
Hallo, > Nice idea. When you have this, then you can even add a context menu > "close context" to the item, for exactly the case where the macro failed > to close it. This way, we could prevent breaking the complete Undo > mechanism in a document - at least the user is able to repair it, then. I'm not sure if this is the right option. Try to think as a common user - visual indicator of Undo stack, Close context menu item in a context menu => confused user. From this point of view, there should be Undo & Redo buttons only and if there is a problem, these buttons should be disabled. IMO Undo stack should be limited to the OpenOffice.org documents only with two functions in the API (something like startUndoBlock(), endUndoBlock()) for them. So, extension can say, that more than actions should be grouped into one Undo action. No more, no less. If you want to implement something like removing a post from blog with Undo action, developer should implement it as an action available from a toolbar / menu. The problem can raise when startUndoBlock() was called and endUndoBlock() wasn't called. There can be grayed item in the Edit menu (Undo action name). When user clicks on this item, dialog can appear with information like this - extension ABC is still working with your document, undo can't be performed, do you want to stop / disable extension ABC? If user hits stop / disable button, extension will be disabled, Undo block will be closed and Undo action will be performed. Otherwise (if user hits Cancel button), nothing happens. Just my 2 cents ... -- Robert Vojta
