Community
Participate
Working Groups
Lately I had to work with launch configurations that cannot be created by the IDE on the fly. E.g. when running OSGi applications, the IDE often cannot decuce what bundles to activate/include in the launch. Thus, I often need to open the launch configuration dialog and create a new config or alter an existing one. In this scenario it would help a lot if there were a shortcut to directly open the launch configuration dialog. Maybe Ctrl+Alt+X, X and Ctrl+Alt+D, D are stll free...
(In reply to comment #0) > Lately I had to work with launch configurations that cannot be created by the > IDE on the fly. E.g. when running OSGi applications, the IDE often cannot > decuce what bundles to activate/include in the launch. > Thus, I often need to open the launch configuration dialog and create a new > config or alter an existing one. > In this scenario it would help a lot if there were a shortcut to directly open > the launch configuration dialog. > Maybe Ctrl+Alt+X, X and Ctrl+Alt+D, D are stll free... You could specify the key-binding yourself on the General > Keys preference page. The actions to bind the keys to are the Run... and Debug... actions to open the launch dialog in run mode and debug mode respectively
(In reply to comment #1) > [ ... ] > You could specify the key-binding yourself on the General > Keys preference > page. Sure, that's what I do when I find my self clicking the same menu entries again and again. Wouldn't it be more convenient (and for those that don't know about the key preferences page) to have the binding predefined?
"Alt+Shift+D, D" and "Alt+Shift+X, X" would be nice for the Debug... and Run... commands. That follows the pattern we already use for Show View ("Alt+Shift+Q, Q" to bring up the dialog).
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
