Minor inconsistent behavior:
When changing the visibility through the layer menu (right click on layer name->Modify->use checkbox for Visible) the file is marked as changed and the file is save-able.
When changing the visibility through the new shortcut (shift + click on layer name) the file is NOT marked as changed and the file is NOT save-able
TESTING with Ubuntu 14.04 +
LO 126.96.36.199.alpha0+ (2016-02-24_23:58:47)
(In reply to Ulrich Gemkow from comment #0)
> When changing the visibility through the layer menu
- Create new file in Draw and save it
- Layers are listed as tabs at the bottom middle of the window ("Layout", "Controls", etc..)
> (right click on layer
> name->Modify->use checkbox for Visible) the file is marked as changed and
> the file is save-able.
- Using the "Layout" layer, I unchecked the Visible box and file became save-able
> When changing the visibility through the new shortcut (shift + click on
> layer name) the file is NOT marked as changed and the file is NOT save-able
CONFIRMED. Behavior should be consistent, no matter which path is used to toggle visibility.
Status -> NEW
Sounds like an EASYHACK
Sounds like an easyHack, but it misses:
- codepointers (mandatory for easyHack)
- set the keyword skill<foo> and difficulty<foo>
- Optionally also set topic<foo>
Marking it as "NEEDING" for now.
Removing keyword 'needsDevEval' as this bug is an easyHack
Changing status: NEEDINFO -> NEW
Adding keyword 'needsDevEval'
Consult, no easyhack
Created attachment 128263 [details]
Proposed patch to fix problem
Thanks for handling this!
I have added an patch proposal which fixes this bug. This patch does not add an undo action (the dialog box adds one). If this is wanted I can try to add this.
I still have problems to setup gerrit (ssh key problem). If someone wants to apply this patch - feel free.
Ulrich Gemkow committed a patch related to this issue.
It has been pushed to "master":
tdf#98587 Inconsistency menu/shortcut for layer visibility
It will be available in 5.3.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.