On 09/11/2007 19:53, Alan Boba wrote:
On Nov 9, 2007 12:00 PM, mike scott <[EMAIL PROTECTED]> wrote:
On 9 Nov 2007 at 16:31, Richard Travers wrote:
...
The point is that OOo appears to allow you to set a document to be saved as
Read Only (Tools>Options>OOo>Security>File Sharing Options...Open this
document in read-only mode) but that it does not appear to work.
What are I and the OP missing, or is this a bug?
On Nov 9, 2007 12:00 PM, mike scott <[EMAIL PROTECTED]> wrote:
Can't answer for 2.1; under 2.3 it seems to behave as expected. Start a
new document, set the readonly option, save, close; reopen -- can't
edit it. Although it's not flagged by the OS as ro. It seems you then
have to save as a new document to get write access back.
Actually, for OOo 2.3 under Windows XP Pro, right click on the
document. The context menu will include an "Edit" item. Click "Edit"
and you're back to normal document with live cursor. At least that's
what happens on my system.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Operating System "read only" operates on two levels: if you *own* the
file it's merely a protection against you accidentally changing the file
(because you can unprotect the file). If you don't own the file it's
pretty secure protection against you changing the file; you'd have to
crack the OS's file protection mechanism - clearly not impossible but
beyond the average user. *nix has a readily explainable concept of
ownership and file permissions, largely because it properly supports
multiple users on the same machine. Although I'm a Windows user I don't
understand its mechanism. Largely because Windows has a really hard time
properly supporting multiple users, especially the idea of *one*
administrator and several non-administrators.
I suppose that if you set OO's "read only" flag then, if the OS will
allow you to change the file then you can presumably unset the flag.
Again, it's only a prevention against *accidental* damage. If the OS
won't let you write the file - as on Windows if you don't own it and it
isn't shared, then presumably you can't unset the flag.
The only reason I can think of for OO implementing its own "read only"
mechanism is to protect users from having to learn the workings of their
Operating System.
--
Harold Fuchs
London, England
Please reply *only* to [email protected]
