When clicking an Insert-shape button, the currently-selected shape should lose focus, as we will now be drawing the shape. However, this is not what happens. What does happen is that the current shape remains in focus; and if you were typing in it, you go out of "typing mode" back to selection of the whole shape, which is distracting..
Created attachment 180442 [details] Video showing the described workflow (In reply to Eyal Rozenberg from comment #0) > However, this is not what happens. What does happen is that the current > shape remains in focus; and if you were typing in it, you go out of "typing > mode" back to selection of the whole shape, which is distracting.. Hi Eyal, I attached a video showing the workflow you described. So, after inserting the first shape and entering text, when I click the shape tool to insert the second shape you would like that nothing was selected? The current implementation seems natural to me. What would be the advantage of having nothing selected? IMO there are two things that could be improved in this workflow: 1) When the user finishes drawing the shape, the shape tool should no longer be selected in the sidebar, since the command is no longer enabled (you can't immediately draw a second shape) 2) If you click a shape tool and give up drawing the shape, it should be possible to press Esc and return to selection mode.
(In reply to Rafael Lima from comment #1) > Hi Eyal, I attached a video showing the workflow you described. So, after > inserting the first shape and entering text, when I click the shape tool to > insert the second shape you would like that nothing was selected? Yes, I expect a de-selection. Note that, in your example, your new text box did not intersect the existing box. It would be more distracting if you intended for the boxes to intersect; and even more distracting if the contour took up more of the shape's area on screen, e.g. a star shape for example. > The current implementation seems natural to me. What would be the advantage > of having nothing selected? 1. User will not be distracted to focus on now-selected shape (the selection indication attracts attention). 2. Contour won't obstruct the view of where you might place/draw the object. > IMO there are two things that could be improved in this workflow: > 1) When the user finishes drawing the shape, the shape tool should no longer > be selected in the sidebar, since the command is no longer enabled (you > can't immediately draw a second shape) > 2) If you click a shape tool and give up drawing the shape, it should be > possible to press Esc and return to selection mode. That would be nice, but would be a different bug :-)
Ok... I guess this can be viewed as an enhancement request. Let's hear the opinion of the UX team about this. (In reply to Eyal Rozenberg from comment #2) > That would be nice, but would be a different bug :-) Indeed. I'll start this discussion in a separate ticket.
The "Insert > Shape" button is not a precise description. Rafaels video considers the Shapes sidebar tab. Selecting and object here is similar to clicking a spin box or single-clicking an entry in the Stylist: you don't execute a function but focus a UI control. It could be seen similarly for the drawing toolbar (and should because of consistency). To click the shape drawing function (for instance .uno:Rect) does not start the drawing process until you click the canvas. Keep also in mind that selecting a toolbar button is necessary for accessibility. You tab over the buttons and "see" via the screen reader.
We discussed this request in the design meeting. (In reply to Rafael Lima from comment #1) > 1) When the user finishes drawing the shape, the shape tool should no longer > be selected in the sidebar... > 2) ...(by pressing) Esc and return to selection mode. This makes sense. The Shapes sidebar should not keep any focus.
(In reply to Heiko Tietze from comment #5) > We discussed this request in the design meeting. Was your design focused only on the side-bar "angle" which Rafael brought up, or are you agreeing with my suggestion generally?
(In reply to Eyal Rozenberg from comment #6) > Was your design focused only on the side-bar "angle" which Rafael brought > up, or are you agreeing with my suggestion generally? True, c1 has some different angle. Don't see much need to unfocus the object when a command/action is _selected_. You are not drawing a shape unless clicking the canvas and that's the moment when the previously focused object is unselected.
(In reply to Heiko Tietze from comment #7) > (In reply to Eyal Rozenberg from comment #6) > > Was your design focused only on the side-bar "angle" which Rafael brought > > up, or are you agreeing with my suggestion generally? > > True, c1 has some different angle. Don't see much need to unfocus the object > when a command/action is _selected_. You are not drawing a shape unless > clicking the canvas and that's the moment when the previously focused object > is unselected. But I get actively distracted by the change in focus, which makes a lot of visual changes in front of me, in places where I was going to draw a box. Sorry I couldn't be in the design meeting to clarify that, but I feel like the app is blinking at me, discouraging me from doing what I wanted to do.
Dear Eyal Rozenberg, 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
Bug still manifests with: Version: 25.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: c8371b5f1a84191d38185820915f0d93741df1fe CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US and IIANM this should be a pretty easy fix.