Description: LO-Draw does reposition the layer tab under cursor to the active layer, when clicked (e.g with SHIFT to hide/show some layer / elements in current drawing). This is confusing and annoying as in cases when there is a large number of layers, not all and especially the active one not visible in view and if clicking on a layer to show/hide a recurrent on/off is not possible as LO-Draw does reposition the tabs view to show the active one under cursor and not as expected the just clicked one. Steps to Reproduce: 1.Create a reasonable number of layers so that not all are visible 2.Move the active layer by scrolling in the layer view out of view 3. CLICK Twice on a layer in visible area to hide/show a layer Actual Results: LO-Draw does reposition the tabs view to show the active one under cursor Expected Results: LO-Draw should NOT reposition the tabs view and stick with the clicked/current one. In other LO Tools (e.g. Calc this is the current behavior) Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.5.2 (x64) Build-ID: dd0751754f11728f69b42ee2af66670068624673 CPU-Threads: 8; BS: Windows 6.1; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Created attachment 164887 [details] Example file (In reply to KrauseM from comment #0) > Steps to Reproduce: > 1.Create a reasonable number of layers so that not all are visible > 2.Move the active layer by scrolling in the layer view out of view > 3. CLICK Twice on a layer in visible area to hide/show a layer Step 3. is misleading: you should *not* double-click, but Shift-/Ctrl-click! Already repro with 4.4.7 and 3.3.0
Let me clarify, I did not mean in #3 a double-click but two distinct single-click operations in a short period of time (say ~1..2 secs) to toggle the visibilty of all elements on the clicked layer to analyze their positions on the current drawing. This is my usual use-case where the problem is really annoying. However as suggested, a single Shift-/ or CTRL-Click on a visible layer while the active one is outside the view already sufficiently shows the issue.
Dear KrauseM, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
AS suggested by QA-Admins: Just did a verification of issue existance: Tested problem in latest LO-Draw version V24.8.2.1 Problem still exists! BTW, In addition to the bug-description, the problem is not only occurring if "Shift" is pressed while clicking on a tab-name after scrolled in a tab previously out of sight, the same problem occurs if "CTRL" is pressed. BR, MK.