Matthew L. Avizinis wrote: > I am writing a macro in which I open other Writer text documents via > ftp either in a new frame or same frame as the currently open document. > I am using beta 1.9.100. I am using currently loadComponentFromURL() > and there are problems with opening the new document in read/write mode, > that is they tend to open read only (btw, this wasn't an issue in 1.1.4 > and it has been suggested to me the perhaps it is now due to permissions > issues that are not addressed in the macro.
You should be more clear: do they get opened readonly *always*? If yes: it could be a problem in OOo. If no (means: only sometimes): I'm a little bit clueless. If permission issues forced OOo to open the file "readonly" they should have been present in OOo1.1.4 also. Hm, maybe the ftp content provider was improved in OOo2.0 and now pays attention to this, but didn't do it on OOo1.1.4? Have to check that. > Also I did not rewrite the macro much for the new beta except to > clean up a couple lines that do things that are apparently fixed in > the new version). Sorry, I don't understand this. Or should that only mean that you don't expect your macro being the culprit? I don't expect that either (see above). > what, if any, methods are there to load/open files other than with > loadComponentFromURL()? And, if so, please give me example code, if > possible. I have looked through the SDK1.1 and haven't seen anything, > but there is so much material and there really isn't a good search > mechanism to go through it all and maybe I've missed something. I don't think that anything like this will fix your problem. We should try to find out what's going wrong. > Here is the function code snippet edited for brevity: ( code snipped - looks OK to me ) > Secondly and secondarily, if I create new regular Writer text documents > with a new extension, e.g. filename.gleim, how do I set up the > association within Oo such that whenever a file with that extension is > opened it will be recognized as of type .odt? You don't need any special extension for this, OOo recognizes its own file types anyway. If you open an OOo file from the OOo file dialog it will be loaded correctly regardless which extension it has. Extensions are only a crutch for the Windows desktop. But I assume that you found a problem in a particular use case I don't see ATM. Can you explain where you want to see such a "recognition"? Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
