open writer -> menubar -> insert there are 3 toggle functions - DrawText - HyperlinkDialog - Horizontal Line why are this 3 items toglle functions with an checkbox, cause nothing happen when DrawText is checked. Same for the other two functions.
Andreas, please add a screenshot. I think it's kde5/gtk3 problem with checkboxes in main menu like bug 123114
that's not related to bug 123114 cause this is not how to show toggles. This bug say the three items should have toggles at all.
The hyperlink dialog is amodal and can stay open while editing. So toggle makes sense. Add Horizontal Line is similar, it adds a ruler at this position until switched off. I'm not sure about the Text Box (guess you mean this with DrawText).
(In reply to Heiko Tietze from comment #3) > Add Horizontal Line is similar... But since switching off doesn't remove the HR I would also rather not toggle it.
When I activate the toggle I would think that this command is activated and I can draw an horizontal line, DrawText, but it's not activated when the toggle is set, so I don't see an benefit of have the toggle.
Created attachment 150773 [details] writer -> menubar -> insert -> toggle
(In reply to andreas_k from comment #0) > - DrawText > - Horizontal Line Should not be there indeed
On Windows builds we don't see a checkbox of course (as noted by Roman), but the "selected" status for a -Draw- Text Box object does not make sense--you can only add one Text box at a time. And as soon as the box outline is made and text entry starts the mode releases. Likewise it doesn't make much sense for its toolbar button to show the selection status either--but that is in the distant past. Suspect a number of these toggled selections are hold overs from how the UNO commands were created/migrated as toolbar buttons first and then picked up as menu items. In that context the Horizontal Rule currently only applies the Horizontal Rule style to a newly inserted empty paragraph--but it used to offer a selection including gallery clipart, and could be toggled? I'm sure there are others across the menus/toolbars where the actions probably need to be tweaked for consistency. And as Heiko notes, the Hyperlink action is amodal dialog, and should provide a toggled selected checkbox.
(In reply to andreas_k from comment #0) > - DrawText This is a toggle, because when checked you're in a draw mode and can draw a text box. (The UI changes too: In the standard toolbar UI, the formatting toolbar disappears, and the drawing object properties toolbar takes its place. In the notebookbar UI, the drawing context activates.) The toggle is mostly important for the toolbar button, as we want it to become pressed after clicking it. There's no way of having the toolbar button pressed, but not having a checkbox in the same command placed in a menu. > - Horizontal Line Technically, this doesn't insert a line, but sets the "Horizontal Line" paragraph style to the current paragraph. I agree that it isn't good to have a checkbox if it isn't possible to turn this off (and probably it won't be possible to implement, as it isn't clear which paragraph style set instead). So either we find a way to hide the checkbox (e.g. wrap the style setting with a new uno command), or simply move this item into the "Styles" menu where it really belongs.
Let's summarize: * Keep Hyperlink as it is; the function dialog is amodal (while I would change this some users would call it a regression) * Untoggle Draw Text (both menu and toolbar); there is no benefit to indicate the draw text function to be active as it is shown by the changed cursor. * Untoggle Horizontal Rule; Unchecking has no effect and it's not repeatable; while technically it is a style users expect to _insert_ a HR so let's keep the position
Is it possible to set in the menubar.xml that there should be no toggle shown? cause as Maxim wrote in the toolbar it can be usefull.
(In reply to andreas_k from comment #11) > Is it possible to set in the menubar.xml that there should be no toggle > shown? cause as Maxim wrote in the toolbar it can be usefull. You have to change the UNO command definition, which applies to all occurrences.
(In reply to Heiko Tietze from comment #10) > * Untoggle Draw Text (both menu and toolbar); there is no benefit to > indicate the draw text function to be active as it is shown by the changed > cursor. I disagree about the toolbar part. While the changed cursor indicates that it's possible now to draw an object, it doesn't indicate *which* object is going to be drawn. It might be a text box, but as well it might be a shape or a frame. Having the corresponding toolbar button pressed is a common behavior in other drawing programs, and I think people will expect it (e.g. see Bug 39478). I really think we need to find a way to fix the menu w/o changing the toolbar. One possible way is to introduce a special attribute for the menu xml, like Andreas suggested. That would also solve the problem with horizontal line. Another approach might be to have a special "toolbar toggle" status type, which will be interpreted by the toolbar, but not by the menubar.
@Heiko, adding 'easyHack' and 'nnedsDevEval' together, plus not adding code pointers doesn't sound right to me...
(In reply to Xisco Faulí from comment #14) > @Heiko, adding 'easyHack' and 'nnedsDevEval' together, plus not adding code > pointers doesn't sound right to me... That's exactly how we agreed on when proposedeasyhack got removed. I vote for reintroducing it.
Dear andreas_k, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear andreas_k, 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