Community
Participate
Working Groups
Build 20020404+
Debug would have to change F5 for step into, which will not happen for M5. Others have complained that our debug shortcuts are inconsistent with other dev envs out there, which all use the same ones (talk to Trent). For 2.0, I suggest we leave it up to the views to hook a key listener if they want to support F5. The Navigator does this already.
Reassess post 2.0
Reopen to investigate
2.1 build 20030114 This would be a nice improvement and make the Eclipse workbench feel more like a normal Windows application. Given the new key bindings support, shouldn't it be possible to have F5 as a shortcut for File > Refresh without having to change Debug?
it is possible with the keybindings support that other parts can override F5, but debug probably wants their keys to work globally, and users will complain either way. for this to ever be resolved, debug needs to give up the key in favour of more standard debugging keys. (is F5 a carry over from visual age?). once debug uses the new key binding support, a user can always remap both 'Step Into' and 'Refresh' commands, so we are really only talking about an out of the box issue. still, Refresh should have more priority than Step Into for initial key bindings in spite of precedent. moving to debug for comment.
I believe we based our key selections on VA/Java and LeapFrog. We should investigate other key bindings, and avoid the conflict.
The only other somewhat standard keybindings I'm aware of are those used by Visual Studio and some other debuggers like the IBM Distributed Debugger. However, note that VS also uses F5, for run/resume. Not sure if the others also use this.
Since F5 is the historical debug "step into" key, we will leave as is. Refresh can be hard-coded to F5 in the navigator if desired, or a key binding could be added and users could remove the "debug" binding as desired. However, to many users will scream if we remove the step binding.
