Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-12-16 Thread Stephan Bergmann
On 12/15/08 20:44, Marten Feldtmann wrote: | writerDocument | writerDocument := aMSKOO desktop loadComponentFromURL: 'file:///c:\test.odt' string TargetFrameName: '_blank' string SearchFlags: 0 long Arguments: Array new. The only thing that catches my

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-12-16 Thread Marten Feldtmann
Stephan Bergmann schrieb: On 12/15/08 20:44, Marten Feldtmann wrote: | writerDocument | writerDocument := aMSKOO desktop loadComponentFromURL: 'file:///c:\test.odt' string TargetFrameName: '_blank' string SearchFlags: 0 long Arguments: Array new. The

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-12-15 Thread Mikhail Voitenko
Hi Marten, As Mathias has written it would really help if you provide the code snippet related to parameters generation of the call. There is currently no known problem in this area, thus the scenario you are using should have a specific that let the problem be reproducible. And to detect

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-12-15 Thread Marten Feldtmann
Mikhail Voitenko schrieb: Hi Marten, As Mathias has written it would really help if you provide the code snippet related to parameters generation of the call. There is currently no known problem in this area, thus the scenario you are using should have a specific that let the problem be

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-12-13 Thread Marten Feldtmann
Ok, I did some further tests: a) deinstalled the 3.0.0 and installed the newest developer build - same error. b) deinstalled the developer build and installed OO 2.4.1 and my software worked without problems It's not a feature ... perhaps just a nasty little bug in the OLE bridge

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-11-26 Thread Mikhail Voitenko
Hi Marten, It looks pretty like as if the document was locked. Strange enough you can still open it in UI office. The only possible scenario with such behavior that I currently see is that the script uses a different office instance ( at least different user configuration ) than the UI OOo

Re: [dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-11-24 Thread Mathias Bauer
Marten Feldtmann wrote: I did some tests with that API call and whatever I do: the document is always opened readOnly. - when I open the document using OpenOffice 3.0 via dialog, the document opens the normal way: writeable - when using the API call I always get a write protected

[dev] OO 3.0, COM, loadComponentFromURL, readOnly ever .... :-(

2008-11-21 Thread Marten Feldtmann
I did some tests with that API call and whatever I do: the document is always opened readOnly. - when I open the document using OpenOffice 3.0 via dialog, the document opens the normal way: writeable - when using the API call I always get a write protected document - when I use the property