When debugging, the context menu command ordering isn't very intuitive.
Two refactoring commands are shown at the top, followed by three navigation commands, followed by the expression evaluator. Finally we get a break, then the debugger stepping commands.
Some thoughts on the UX:
Refactoring commands aren't very useful when debugging as we don't support edit and continue (and even if they were, they don't seem as relevant as debugger commands)
The Cmd-F10 shortcut for "Run to Cursor" is bad, F keys are not very usable on Macs.
What's the expression evaluator? Why wouldn't I just use the interactive window? Why is is grouped with the navigation and refactoring commands?
The most important things should be at the top. That's probably navigation and run to cursor.
mhutch
commented
6 years ago
When debugging, the context menu command ordering isn't very intuitive.
Two refactoring commands are shown at the top, followed by three navigation commands, followed by the expression evaluator. Finally we get a break, then the debugger stepping commands.
Some thoughts on the UX:
Cmd-F10shortcut for "Run to Cursor" is bad, F keys are not very usable on Macs.