I'll use ManagedMenuButton together with NotebookbarToolBox + GtkToolButton the problem is that ManagedMenuButton works ok in linux but on windows the Size is different.
would it be possible that you can move ManagedMenuButton into NotebookbarToolBox. because with NotebookbarToolBox you can define the icon size and if you'd like to see a label or not.
Created attachment 132676 [details]
ManagedMenuButton work fine in Linux but not in Windows. In addition it would be awesome if the icon size will follow the setting in LibreOffice setting. In sfxlo-NotebookbarToolBox you can define Icon Size and if you didn't select an setting it was used from LibreOffice settings.
So I think if it will be possible ManagedMenuButton move into NotebookToolBox it would be easier to have the same size on all operation systems.
I guess the version is 5.3.2 RC2 (release). If I am wrong, please change it to the correct value.
Best regards. JBF
it's master from 17.04.2017
It's not only the arrow size. It would be very usefull if it's possible to define the button size like in NotebookToolBox
the right buttons are ManagedMenuButtons which the designer have to define in size and the left ones are sized according the LibreOffice configuration.
In addition the File, Edit, Styles, ... Buttons are ManagedMenuButtons they should have the size menu like the print icon right to Menu. This would work in KDE but not in windows.
I have large down arrows on Linux gtk2, so it seems only your KDE build has small arrows.
@Steve, @Alex: Can you attach a screenshot of the Contextual Groups or Groupedbar Full variant of the notebookbar?
** Please read this message in its entirety before responding **
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 http://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!