CONNECT - Pull Down menus

Ian,

I've been experimenting with Screen menus.

Sample can be found here.

http://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/davidgs_blog/archive/2015/10/31/screen-menus

Advantages are.

They are not subject interface changes.

Can be used with key strokes and/or mouse clicks.

Appear where your working, not on the perimeter.

More control over appearance, size, etc.

Graphic in nature so no programing requried.

David

I have played with these in the past. They are good, but can look cluttered and ugly due to the icons. Do you know if you can have a right click and display a popup similar to the right click (hold) menu in CONNECT ie text driven

Also, in your blog, where does the dgnlib file live to make it work?

Thank you for the reply

Ian

The file needs to be in a path MS_GUIDGNLIBLIST uses.

Buttons. Any place you can call a key-in command. Not sure if you can add hold actions to the button menu.

I believe the sample screen menu delivered with MS include a pulldown type menu. You can make them as pretty or ugly as you want. You don't need to use icons at all. Only issue I ran into is small text doesn't render very cleanly due to some limitations on how MS renders the overlay.

I'm a keyboard person so I use space bar to start. My attempt is to emulate a dynamic on screen keyboard.

I'm guessing mine looks ugly because I'm throwing out a lot of information. Personally I don't notice it because at this point I'm just doing 2 letter keystrokes and don't even pay attention to the screen part. But in my opinion a beginner need to develop the Letter/Command association so it need to be obvious from the start, thus the clutter. However you are not restricted to keystrokes. I can also just click on the screen.

Regards,
DavidG

The file needs to be in a path MS_GUIDGNLIBLIST uses.

Buttons. Any place you can call a key-in command. Not sure if you can add hold actions to the button menu.

I believe the sample screen menu delivered with MS include a pulldown type menu. You can make them as pretty or ugly as you want. You don't need to use icons at all. Only issue I ran into is small text doesn't render very cleanly due to some limitations on how MS renders the overlay.

I'm a keyboard person so I use space bar to start. My attempt is to emulate a dynamic on screen keyboard.

I'm guessing mine looks ugly because I'm throwing out a lot of information. Personally I don't notice it because at this point I'm just doing 2 letter keystrokes and don't even pay attention to the screen part. But in my opinion a beginner need to develop the Letter/Command association so it need to be obvious from the start, thus the clutter. However you are not restricted to keystrokes. I can also just click on the screen.

Regards,
DavidG

David

the referral to UGLY wasn't aimed at your setup. Just what I have found in the past versions ie ss3

I like the sub categories and I will see I can replicate this from my old menus

NOTE: It would still be nice to have a pull down menus

Thank you

David

How did you manage to get some menus to be greyed out and inactive?

Ian

For the menu I have the view rendering set to Smooth, not wire frame.

In the graphics file I place a semi-transparent shape over the inactive ones.  

They are inactive because I haven't assigned a key-in/command to them yet.

Because you can use rendered 3D graphics you can make some pretty cool looking stuff.  

Initially I had 3D keys however ended up opted for more of a simpler look.

.

You can import menu customizations into the ribbon using the Customize Ribbon dialog. Set the "Choose components from:" picker to "Menu Customizations". You can drag them into a Group or the QAT as button or as an item within a Drop Down or Split button.