I've made a new workflow with one Tab. In this tab I've created 10 groups with different commands and different size of icons. When first created, the layout looks all fine. All groups fit well and there is a lot of space left at the end of the ribbon.
After closing and reopening MicroStation, the initial state of the ribbon is resized, where the 'large icons' are shown as 'Medium' or 'small', leaving even less space at the end of the ribbon.
Changing the workflow to 'Drawing' and then change it back to my workflow the groups are resized back to their designed size.
Is there a way to prevent the groups from resizing? I have tried to set MS_RIBBON_NUMEXPANDEDTASKGROUPS to a higher number (12), but that didn't resolve the problem.
Paul
~~
Can you share the dgnlib in which the tab was defined for review. How did you define the size of the buttons?
The default size should be defined in the customize ribbon dialog. If you right clicked on a button and resized it that way the settings may not be saving.
Also can you post larger and higher resolution screenshots
Hi David,
I defined the size of the buttons per button in de Customize Ribbon dialog box.
The Optimize_NLCS_GUI.dgnlib is the one with the unwanted behaviour, the Optimize_Tools_Menu_CE.dgnlib is referenced by Optimize_NLCS_GUI.dgnlib (the last group in the NLCS_Gui ribbon is defined in the Optimize_Tools_Menu_CE.dgnlib).
Optimize_Tools_Menu_CE.dgnlibOptimize_NLCS_GUI.dgnlib
Hi Paul,
I have two comments to the discussed issue, unfortunately none from them can be treated as final answer:
I see the same behavior (I just placed dgnlibs to folder and start MicroStation). It is weird, but without knowing exactly the internal process how ribbon definitions are loaded and evaluated, it is I guess impossible to find the reason of the problem.
It looks like ribbon or group size is evaluated wrongly at the beginning (or some small default value is used?), but when the ribbon is re-evaluated (e.g. using "ribbon rebuild" key-in), sizing and positions are corrected.
I would treat is as bug, because when nothing changes, ribbon content should not change too.
My second comment is about the tool, used to define complex ribbon for NLCS application: In my opinion, to use ribbon customization GUI based tool is wrong. It is very limited, buggy, and does not allow to use full potential of ribbon, that can be used to implement good GUI.
When ribbon definition, defined by xml (and compiled to .rsc optionally), is used, much more (5x - 10x) features can be defined for every ribbon control, like exact sizing and collapsing rules etc. A disadvantage of this approach is that to write xml manually is required (but .xsd is available, so validity is ensured). Definition format is part of MicroStation SDK documentation, but honestly, it provides basic description only (so as usually, to play with the definitions to obtain experience is required ;-)
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi Jan,
Thnx for your reply.
"I would treat is as bug, because when nothing changes, ribbon content should not change too."
I will report this as a bug.
By the way: Ribbon Rebuild does not solve the problem. I have to load another tab or another workflow.
"My second comment is about the tool, used to define complex ribbon for NLCS application: In my opinion, to use ribbon customization GUI based tool is wrong. It is very limited, buggy, and does not allow to use full potential of ribbon, that can be used to implement good GUI.
When ribbon definition, defined by xml (and compiled to .rsc optionally), is used, much more (5x - 10x) features can be defined for every ribbon control"
You're right, and that is exactly what we are doing.
"A disadvantage of this approach is that to write xml manually is required"
Therefor we use the customized GUI Ribbons as base for our .xml and .rsc so a cad manager or key-user without knowing how to set up a proper XML can make his own customizations which than can be included in our .rsc.
Paul Haffmans said:By the way: Ribbon Rebuild does not solve the problem. I have to load another tab or another workflow.
It works fine on my computer, and in fact it is exactly what MicroStation does at the background, when new workflow is loaded. Probably some tiny local detail (ribbon size, resolution...?) plays a role there.
Regards,