Migration and migraines need help

Bar menus won't work in Connect. If your complaint is just that ribbon takes up too much room, on the far-right of the ribbon is a ^ icon. Click that to minimize the ribbon to a menu bar. The ribbon then shows up when you click a menu option and disappears when you're done.

Kevin As you can see my menu customizations is vast. The dropdowns you see are setting level, symbology, etc. And this case setting a multline style and invoking the mline command. Others may set the level and Smartline command and  Tell me how to customize Ce to get this fast production, please. Templates could work if they allowed you to assign a command too, but it doesn't

I've had some success having the old top bar menus show up in CONNECT in my Quick Access Toolbar just by referencing the older dgnlib file in my CONNECT configuration.

If that doesn't work you can add standard Toolboxes (both default and custom) to the Quick Access Toolbar and they will mimic the older bar menu.

I'm more a workspace person than a ui customization expert, If you want to try and duplicate that with a ribbon setup I would create your own Workflow and populate it with panels and buttons and drop-down menus. A Workflow consists of the Ribbon Tabs and Groupings with in the ribbon tab and then commands in the group.

So if you open Customize Ribbon, click the New Workflow button in the right-panel, I called this My Buttons. This created an entry in the drop-down under the workflow in the title bar. Then I created a Home tab under that and just copied the Home tab options from another workflow. Then I created another tab to duplicate one of your menu options 1CW. Under that I created a panel U-Below and just kept creating panels (these sub-panels don't appear in my ribbon, but they make it useful to group items.)

Then finally I created buttons. You can assign key-ins to buttons.

Another option would be to make the 1/2 Ply panel a Drop-Down menu with 1/2 PLY BELOW and 1/2 PLY MASK as options underneath it. That would tighten up how many buttons you had appearing in the ribbon.

Note that this ribbon setup is quite a few clicks less than your old setup. Assuming you already have your Workflow selected it's 1 click to select a ribbon tab, and a 2nd to select the tool. Your screenshot is 5 clicks each time you want to change a tool.

if it is a common tool that is delivered such as place smartline. The why not simply create templates ? 

load the needed template for the symbology then pick the needed tool (place smartline).

if it is a common tool that is delivered such as place smartline. The why not simply create templates ? 

load the needed template for the symbology then pick the needed tool (place smartline).

Generally people want a single button to do all the actions, which is perfectly doable, create a button that picks the template and triggers smart line for you. Then you don't have to do them separately, and if you change the template the button already picks the latest version of the template

Tim

My way avoided creating a template. The menu would set the level , symbology and multiline and the m line command

Below no need to create a template. Why set up a template and then another custom command that calls up the template and the command. 

LV=CW-full;active symbology bylevel;MlineStyle Edit Style "ply 3/4";MlineStyle Active Selected;place mline constrained

There are several advantages of templates:

the first only really matters if you have different standards you switch between. If one standard calls for your ply 3/4 to be on one level, and the other other standard calls for it to be on a different level then when you switch standards as long as the template names are the same the same button works for both standards.

Your key-in could be:

lock templateassociation on;template active 3-4Ply;place smartline

now whatever standard you use that has a 3-4Ply template works with the same button.

Another advantage is if you have to modify your existing standard you don't have to find every button you set something on. Just change the template and the buttons still work correctly.

The last advantage I'm aware of is in reporting. Since an element knows what Template was used when created you can do things like build quantity take offs based on template names rather than super-specific leve/weight/color mappings.

If you have multiple tools that share the same symbolgy settings.

You are merely mentioning one function for those settings.

workflow might be: pick template and it sets the symbology, then pick various tools needed (place line, place arc, etc...) . Pick a different template to set new symbology, then pick the same tools in the same location (place line, place arc, etc...) 

One tool, multiple templates.

just saying.....