Re: [api-dev] Unfortunate document event name - how to fix it?

2009-05-18 Thread Bernard Marcelly
Message de Ariel Constenla-Haile date 2009-05-14 17:04 : Hello Mathias, On Wednesday 13 May 2009, 14:14, Mathias Bauer wrote: The best documentation is an API that doesn't need one. This deals with the fact that people don't like to read documentation. Having speaking names for events is a

Re: [api-dev] NB plug-in: Debug Extension in Target OOo fails on OOO310_m11

2009-05-18 Thread Steffen Grund
Hello Ariel, this happens for me (on Solaris x86) even without NetBeans etc. I simply add e.g. -Xdebug -Xrunjdwp:transport=dt_socket,address=8701 as parameters to the JavaVM in OpenOffice.org. The next time I start OpenOffice.org, I get the message box stating the JRE is defect. I cannot

Re: [api-dev] NB plug-in: Debug Extension in Target OOo fails on OOO310_m11

2009-05-18 Thread Stephan Bergmann
Sounds like a consequence of http://qa.openoffice.org/issues/show_bug.cgi?id=101457 javaldx searches for Java on every startup. -Stephan On 05/18/09 10:37, Steffen Grund wrote: Hello Ariel, this happens for me (on Solaris x86) even without NetBeans etc. I simply add e.g. -Xdebug

Re: [api-dev] NB plug-in: Debug Extension in Target OOo fails on OOO310_m11

2009-05-18 Thread Ariel Constenla-Haile
Hello Stephan, Steffen, * On Monday 18 May 2009, 05:45, Stephan Bergmann wrote: Sounds like a consequence of http://qa.openoffice.org/issues/show_bug.cgi?id=101457 javaldx searches for Java on every startup. yes indeed, and your patch has fixed it on my DEV300_m48 :-) Log attached here

[api-dev] In memory documents

2009-05-18 Thread Elvis Ciocoiu
I'm want to load/save documents in ooffice from a database. From the documentation it seems that this it will work using a temporary file. My problem is that after loading the document and after the user did some modifications to it the document is dirty. And if the user is trying to close the

Re: [api-dev] In memory documents

2009-05-18 Thread Christoph Jopp
Hello Elvis, I don't know if this is what you are looking for, but I think you could implement an css.util.XModifyListener and catch the modified() event. f.e. to set the modified-flag of the document to the desired value. The setModified method is accessible via the css.util.XModifiable

Re: [api-dev] In memory documents

2009-05-18 Thread Elvis Ciocoiu
It seems like a good solution. I implemented a listener to XDispatchProviderInterceptor an register it in the frame. I've intercepted the urls uno:CloseWin and .uno:CloseFrame and forced a save fo the current document (if is one loaded from the database). That way I'll still have the document