Stephan Bergmann schrieb:
<file:///E:\Test.ods> is not a valid URL to denote Windows pathname
E:\Test.ods (<file:///E:/Test.ods> would be correct). I vaguely
remember that the implementation of loadComponentFromURL indeed does
somewhat strange things upon such invalid input (which would explain
the read-only status; maybe there is already an issue for this?).
(By the way, <E:/Test.ods> is also not a valid URL to denote Windows
pathname E:\Test.ods; it is an URL of the---unknown---schema "e".
That loadFromURL happens to work "as expected" for such invalid input
is a sad consequence of "try to guess what the client wants" software.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
I didn't know if loadFromURL can handle E:/Test.ods as well since my
converting function adds file:/// and gets rid of backslashes to get a
valid file URL ( file:///E:/Test.ods ). But tested it and at least there
it throws an error and does not open in read only mode or sth. like that.
An error on ALL kinds of invalid urls would be great. Would make
debugging easier.
Steffen Börsig
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
