<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - FILEOPEN: "Open" in "Document in Use" dialog for non-default file format documents opens read-only"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=107443#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - FILEOPEN: "Open" in "Document in Use" dialog for non-default file format documents opens read-only"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=107443">bug 107443</a>
from <span class="vcard"><a class="email" href="mailto:baron@caesar.elte.hu" title="Aron Budea <baron@caesar.elte.hu>"> <span class="fn">Aron Budea</span></a>
</span></b>
<pre>(In reply to Thomas Lendo from <a href="show_bug.cgi?id=107443#c6">comment #6</a>)
<span class="quote">> I tested it on Ubuntu Linux and there the "Open" button has the correct
> meaning (it's "stealing" the edit mode from the other instance).</span >
There are three kinds of behaviors when opening a file based on what is in the
lock file (provided the file isn't actually locked):
- if all the details are the same as your current user and profile, the file
will open without question,
- if the profile location is different, the program will assume that the same
user had the file open from a different system, and will let them open the file
for editing,
- if the user name is different, the program will assume the file is locked by
someone else, and will only allow opening it in read-only mode, or as a copy.
Of course file system locks can override user action, there's no real way to
"steal" edit mode if a file system lock is in place (unless by tinkering on OS
level).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>