Issue 112808 - "Edit File" button produces misleading message for locked files
Summary: "Edit File" button produces misleading message for locked files
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2010-06-30 08:40 UTC by dalez
Modified: 2014-02-04 19:59 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description dalez 2010-06-30 08:40:06 UTC
The "Edit File" button produces the wrong or misleading message for locked files.

Scenario 1:
User A has a document open for editing
User B has the same document open in read-only mode
User B clicks on the "Edit File" button to edit the document
User B is presented with the message "This document cannot be edited, possibly
due to missing access rights. Do you want to edit a copy of the document?"

Scenario 2:
User A has a document open for editing
User B attempts to open the same document in edit mode.
User B is presented with the "Document in Use" dialogue.

Since from a user perspective both scenarios are equivalent, I believe the same
message ("Document in Use") should be presented in both cases. i.e. scenario 1
represents a bug.

The current behaviour is less than friendly in my work environment because of
how we have have set up openoffice to handle multiple-access documents.
Specifically, we have added the "-view" argument to the file-open registry
key(s) so that users always open documents read-only when opening from a file
explorer window. Users have been trained to click the read-only button to edit
the file, then click it again when editing is complete. This imperfect system
usually prevents others who wish to edit the same file from being unnecessarily
locked out.

The unfriendly aspect of this process is that a user always gets the "missing
access rights" message instead of the "Document in Use" message. We presently
have the file explorer set up to view hidden files so we can find the lock file,
open it, and read who the culprit is.