On 10/26/2010 05:26 PM, Chris Rider wrote:
As you can tell from the log file, the close method is being called, but
not the dispose.
Do I need to dispose also? Couldn't really find enough documentation to
figure out *exactly* what those two methods entail. I kind of assumed it
was something
Hi Andrew,
Although I am ignorant in much of this, I do have some random thoughts.
appreciated, as always :)
Mathias Bauer mentioned allowing the container to control changes for
some items (such as he did with notes2), but that this may be a problem
with larger objects such as graphics
Hi Ingrid,
I think a new UndoFailedException is better than css.uno.Exception. A
client can react on this with a small cleanup of whatever UndoStack
related doings and than proceed further. While catching a
css.uno.Exception the proper reaction is much more unclear. Maybe it is
necessary
Hi Stephan,
- Normal return; the underlying data model is in a state where the
respective changes are indeed undone.
- Exception failed for some reason, undo call completely rolled back,
i. e. the underlying data model is in the state it was in before the
call to undo. It would
On 10/27/10 10:14, Frank Schönheit wrote:
In reacting on the error during Undo, I don't see a real difference
between Exception and a specific UndoFailedException. However, in
using the API, and maybe propagating exceptions up the stack, a specific
exception is slightly better for knowing what
Hallo all,
I tried to implement a com.sun.star.lang.XEventListener on a
code-created Dialog, the Listener is not working. I used the same
Listener on loading a manuel created Dialog from a library, here the
listener works a expected.
Please test my code if we have a iussue or a fault in
