UI: Insert textbox button marked active while cursor inside textbox
Steps to Reproduce:
1. Open Draw
2. Press F2 to insert a textbox & look at the textbox button in the toolbar
The Insert textbox button is active. It seems that you are inserting a new one
The Insert Textbox show only glow when it's clicked to INSERT a textbox. Not when entering an existing textbox
User Profile Reset: No
Version: 220.127.116.11.alpha0+ (x64)
Build ID: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US
Build ID: 169a10f0e4680814145b668c6320be04038d7a89
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.19; Render: default;
don't know if it's the expected behaviour though.
Adding the UX team
The button/command also enters the edit mode (click on the frame and press button or F2). Not really needed but consistent with the enabled state. WFM, Telesto?
(In reply to Heiko Tietze from comment #2)
> The button/command also enters the edit mode (click on the frame and press
> button or F2). Not really needed but consistent with the enabled state. WFM,
That's 'part' of my problem. The button shouldn't have multiple functions. It's confusing.
- As in instrument to insert a textbox (the square) (text draw mode on/off)
- Indicator for being inside a textbox (textbox or shape text)
- As a button to access the shape textbox
The shape textbox 'exists' anyhow. It isn't inserted/ added. It's only 'activated'.
I know 'toying' around isn't representative for a workflow, but I have 'pressed' insert textbox multiple times while having a shape selected. Intending to insert a new textbox. Not activating the shape textbox (which I tend to access with double click). Similar the deselection happening when pressing insert shape, while a shape is active.
In my world, I click Inserting a textbox button to insert a textbox (exclusively the blue square). It's active until a textbox is draw.
Accessing a textbox (shape/or square) should be done by double click/F2 (without further indicator).
Enabling 'Insert textbox' pressing F2 with nothing selected is also fine with me. The 'draw textbox' button is marked active until the textbox is drawn.
This issue didn't exist (by default) in 18.104.22.168. The toolbar didn't have a 'insert textbox button at all'
Maxim, what's your opinion?
Discussed in the past in Bug 113171.
(In reply to Telesto from comment #3)
> but I have
> 'pressed' insert textbox multiple times while having a shape selected.
> Intending to insert a new textbox.
I believe this is the biggest problem here: Users aren't able to insert a textbox while a shape is selected. For comparison, Inkscape also has similar "Text mode" button, but unlike LO you can draw new textboxes while in edit mode of another textbox. Might be a good idea to have similar behavior in LO.
Otherwise, we can introduce a dedicated "Insert textbox" command that will do only that, and use it in the toolbar/menu instead of the current command. The current command that in use in Draw is .uno:Text, but in Writer it is .uno:DrawText, so we can implement .uno:DrawText for Draw too, for a Writer-like behavior. The downside from this is that the menu/toolbar tooltip will no longer show the keyboard shortcut (F2), as it will be a different command.
Finally, if we think that indicating the edit mode isn't useful, we might just change the existing command to not toggle in this case (but only when drawing a new text box). But this alone won't solve the problem of not being able to draw text boxes when another shape is selected.
Simply disable the command while in edit mode, my take.
So let's do it and disable the _insert_ text box command while in edit mode.
*** Bug 134590 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #6)
> Simply disable the command while in edit mode, my take.
This will make it even more confusing. Imagine a user who want to insert a text box, but it happens that he has a shape or another text box selected. He is clicking on the insert text box button, but then suddenly that button becomes disabled. He then might try to draw the text box anyway, with no success. The benefit of keeping the button enabled, is that the user can at least click on the button again, which will allow him finally to draw the text box. And as said in comment 5, there's no reason why we can't make it possible to draw text boxes while another shape or text box is in edit mode. So the first click on the button should be actually enough to also enable the insertion mode.
In addition, I believe the confusion discussed here was mostly caused by the fact the button has a tooltip "Insert Text Box", which is incorrect, as the button is actually a "text tool" button. In the distant past this command used to be called just "Text", and was only present in the toolbar, and not in the Insert menu, so there was no confusion back then. But at some point in time someone decided to add it to the Insert menu, and to rename it to "Insert Text Box". So I think that at least the toolbar button should be renamed back to "Text".
(In reply to Maxim Monastirsky from comment #9)
> button is actually a "text tool" button. ...
> So I think that at least the toolbar button should be renamed back to "Text".
With just noun like "Text" it is totally unclear what it does. Edit, delete, add... many different actions are used on the commands. That's why I always vote for <Verb> <Noun> combinations. "Insert Text Box" sounds good to me and we could make it "Insert/Edit Text Box". But way too much fuss about terminology and preferably the actual issue, to insert a text box while in edit mode, should be solved. Three options: a) rename carefully, b) resolve as WF, c1) resolve and create another ticket for the edit/add thing or c2) hi-jack this request. My take after all the discussion is b) (or c1).
(In reply to Heiko Tietze from comment #10)
> a) rename carefully,
Unfortunately I can't see how it can be renamed then. Using 2 verbs is bad, and also won't work for the Insert > Text Box menu item.
> b) resolve as WF
Possible, but I'm not sure given that there appear to be real reasons for confusion here.
How about this:
1) We keep the current naming as-is.
2) Clicking the button/menu item (or pressing F2) while a shape is selected continues to enter its text edit mode, but _in addition_ allows to draw another text box. The button/menu item is toggled until the text edit mode is cancelled or a text box is drawn.
3) Double clicking on a shape to enter its edit mode, will not toggle the button.
(In reply to Maxim Monastirsky from comment #11)
> How about this:...
Seems to be a good solution.
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!