https://issues.apache.org/ooo/show_bug.cgi?id=122082

Ariel Constenla-Haile <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #17 from Ariel Constenla-Haile <[email protected]> ---
(In reply to comment #16)
> - I can not reproduce the missing activation of panels after a read-only
> document is made read-write

What steps are you following? This isn't reproducible if the file is read-only
(missing user rights, or the like). But if you follow the steps in comment 8,
this is still reproducible. There is a big difference in .uno:EditDoc if the
file is read-only or the document was just opened read-only by checking the
filepicker box:

Test A:

New writer document
Type dt and press F3 to insert dummy text
Save the document and close it
Open the document, checking the "Read-only" checkbox
The sidebar displays the Navigator only, all other panels are disabled
Press "Edit File" from the standard toolbar (.uno:EditDoc), the document will
be editable, and all toolbar items are enabled

Bug: the sidebar does not react to this, it is still in its "read-only" mode,
showing only the navigator.

This is still reproducible on current trunk.


Test B (sorry, Linux instruction to set the file read-only):

New writer document
Type dt and press F3 to insert dummy text
Save the document and close it
Change the file permissions: chmod -w </tmp/Untitled\ 1.odt>
Open the document. It is read-only.
Press "Edit File" from the standard toolbar (.uno:EditDoc), an InfoBox asks you
if you want to edit a copy, press "Yes" to confirm.

There is no bug here, it is another document. In Test A it is the same
document, it's not even reloaded.
Listening for status updates of ".uno:EditDoc" is good, but in
sfx2::sidebar::SidebarController::statusChanged() 

SwitchToDeck(msCurrentDeckId);

doesn't do much. It should update the whole configuration.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to