Am 25.10.2010 14:37, schrieb Frank Schönheit:
XUndoAction, XUndoManager, XUndoManagerSupplier - find the generated IDL
for the proposed API at
http://udk.openoffice.org/files/documents/23/4795/undo.zip
Updated this, just in case somebody wants to have a look at the current
evolution.
Anybody having an opinion on
1. whether XUndoManager.undo/redo, when invoked while an Undo context
is open, should
a. throw
b. silently and implicitly close all open contexts
c. ignore the call
d. other?
2. whether XUndoAction.undo/redo should be allowed to raise exceptions
(except the always-possible RuntimeException)?
3. how to deal with XUndoAction.undo/redo throwing an exception?
a. silence the error?
b. propagate the error to the caller of XUndoManager.undo/redo
c. clear the respective stack, since obviously the top action cannot
be invoked, thus the other actions, which may depend on the top
action, also can't
d. both b. and c.
I tend to 1a., 2-yes, and 3d., but would appreciate any opinion on this.
Agreeing to all, 1a to "educate" the user of the API to correctly close
open contexts... :)
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org
For additional commands, e-mail: dev-h...@api.openoffice.org
