Add new comment

Right, I expected that's the case and can certainly respect the decision to not get into the business of manipulating the mouse cursor.

That said, this feature has introduced an ill side-effect which I spoke to in one of yesterday's responses. Since the "toggle" doesn't have it's own shortcut, and instead is scoped both of the Edit Off and Edit On shortcuts, it is now possible to drop into a MIDI Edit workflow and NOT understand what mode is currently set. By the time the user clicks the mouse, it's too late. Assuming the end user is going to make an optional toolbar visible and move their eyes back and forth between an included icon and what they're actually working on is ......... not the right answer.

Can this be refactored as follows? A new shortcut is made available... call it something like Edit On/Off Toggle. When it is configured with a value, it overrides any values set in the Edit Off and Edit On shortcuts. If no value is set, the individual Off and On shortcuts are respected.

This design would allow the user to opt into this toggle if desired. Otherwise, the user would be free to operate in a backwards compatible fashion.