On Jan 9, 2008 11:55 AM, Frank Schönheit - Sun Microsystems Germany <[EMAIL PROTECTED]> wrote:
Hallo, I forgot to mention, that my comment's are from common user & extension developer point of view. > There's more than this. In fact, there are actions on a document which > are *not* covered by the "native" Undo operations. Especially via API, > you can do things which will never appear in the Undo stack. I can talk > about my domain here only (I could name you a few scenarios with form > controls), but I suppose there are others, too. shouldn't be these operations covered by the native Undo operation? It means, all document changes via API should be saved as Undo operations. > Interesting idea. While it is not possible (architecture-wise) to > execute an action on a grayed menu item, the item could be available, > but show some text "not possible: running action", or something like > that, and then behave as described by you. Maybe some different color or maybe animated menu item image (Undo icon + clocks or something like this). The idea behind this is that there will be no new control (button, whatever), but the old one can be extended. -- Robert Vojta
