General Feedback

Bind engine mode button to keyboard shortcut?

Started by GreenMoose on 2,516 views

Hi,

Have I understood it correctly that with vs2019 the extension menu is no longer accessible via the Alt-keyboard shortcuts as below with vs2017?
[img=https://i.imgur.com/RcT4Slp.png]Engine modes vs2017[/img]

If so, I need to start getting used to the new engine mode toolbar button instead and thus have some suggestions to ease use of it compared to the main menu:
1) Make this button accessible via customizable keyboard shortcut (e.g. Ctrl+M,Whatever) so I don't have to use mouse to switch engine mode.
2) As in the vs2017 engine menu, consider number the engine modes in the drop-down and makes these default shortcut unless one is specified in the engine mode name (such as &Manual in below example).
3) Consider include the shortcut bound to the Customize Engine Modes menu item (Ctrl+M,G in above example) to keep the behavior similar to existing menu.
[img=https://i.imgur.com/3LH7AIV.png]EngineModeButton[/img]

Thanks.

Edited

Your understanding is correct. The loss of our top-level menu introduces a serious regression in keyboard shortcut capability in NCrunch.

We have a wave of UI changes in the works to address this. Unfortunately we didn't have time to put these in place before the first VS2019 test build, but hopefully we'll have something to show in this space in the next few weeks.

Post a reply

Log in to reply.