Hi Daniel, >> 1. whether XUndoManager.undo/redo, when invoked while an Undo context >> is open, should >> a. throw > ... > Agreeing to all, 1a to "educate" the user of the API to correctly close > open contexts... :)
:) Education is a good Thing (TM), I agree. There's one point in favor of auto-closing open contexts: There might be script errors, which leave the stack in a corrupted state. At the moment, there would be no chance to correct this - except by trying to leave as many contexts as possible, which is somewhat cumbersome. (At the UI, you wouldn't even have this possibility: If a broken script leaves a context open, then the non-script user has no chance at all.) However, I plan to (at least evaluate whether to) auto-close all open contexts after running a script. That is, if you'd bind a script to, say, some toolbar item, and this script is ran, then the framework could close all contexts left behind by the script. This would still allow for education of API clients :), but wouldn't bother the user too much with the results of broken scripts. Ciao Frank -- ORACLE Frank Schönheit | Software Engineer | frank.schoenh...@oracle.com Oracle Office Productivity: http://www.oracle.com/office --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
