[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    [Bug 77185] Open a file in read-only mode if it has already been
From:       "Joao S.O.Bueno" <gwidion () mpc ! com ! br>
Date:       2007-03-18 2:12:23
Message-ID: 20070318021223.2764.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=77185         




------- Additional Comments From gwidion mpc com br  2007-03-18 03:12 -------
In reply to #6 -
whenever authomatic detecting of a file change cannot be done at the time it happens, \
warning the user at save time should be enough (and not doing so, would be a bug in \
itself).

I still say this Windows-like, lock users out approach, is simply broken.

BTW, I think a "read only mode" is broken enough. I do not even know - is such a \
thing implemented in koffice? I know it is there in OO, and I dislike it a lot.

> - It would be better than nothing, but being notified that 
> you may have issues with concurrent changes *before* you make   
> yours is a far superior solution, IMHO. 

I'd be allright with "being notified". Locking me out, is another issue.
____________________________________
koffice mailing list
koffice@kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice


[prev in list] [next in list] [prev in thread] [next in thread]