| Summary: | Terminate and relaunch does not work | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Alexander Glass <alexander.glass> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bsi.msa, Michael_Rennie, pawel.1.piech, remy.suen |
| Version: | 4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Alexander Glass
That option will be enabled when you have stuff selected in the 'Debug' view. Are suggesting that while working in the Java perspective, I need to switch to Debug perspective then move the mouse to click in the debug pane and then use the terminate and relaunch keystroke? That hardly seems efficient. Might as well just stick to using the mouse but that defeats the whole point. The ability to relaunch via a single keystroke seems like an essential feature for efficient workflow. (In reply to comment #2) > Are suggesting that while working in the Java perspective, I need to switch to > Debug perspective I mentioned the 'Debug' view, not the 'Debug' perspective. > then move the mouse to click in the debug pane and then use > the terminate and relaunch keystroke? There are keybindings available to switch views. > That hardly seems efficient. Might as > well just stick to using the mouse but that defeats the whole point. The > ability to relaunch via a single keystroke seems like an essential feature for > efficient workflow. But yes, I agree with you in that it is not an efficient workflow. I have no idea how much trouble it would be to make this keybinding work universally in all windows/dialogs but thanks for acknowledging that it could be improved. Also see bug 198991. (In reply to comment #4) > I have no idea how much trouble it would be to make this keybinding work > universally in all windows/dialogs but thanks for acknowledging that it could > be improved. Its not so much about 'making it work' - it already works - the issue is that it is selection sensitive: it terminates the selected launch. My advice would be to add the Debug view to the perspective of your choosing, and shrink it down to breadcrumb mode. That way it is always there and the actions should work just fine. here is some more information on breadcrumb mode: http://help.eclipse.org/helios/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Freference%2Fviews%2Fdebug%2Fref-breadcrumb.htm While the debug breadcrumb mode seemed promising, it requires me to select the active context after each relaunch. Maybe there is a way to have the debug breadcrumb mode automatically select the a context but I am not seeing it. If you are debugging multiple applications simultaneously then the need to select the current context to relaunch makes sense. If there is only a single context open, this should be terminated and restarted. Maybe I spoke too soon as this functionality "works" only if invoke the application with debug mode. If you simply run the application the breadcrumb mode does not automatically select the current running context. Maybe the solution is to have the console window support its own restart mechanism. A restart button next to the stop button would be nice. Also a keybinding to restart the active console would solve this problem and not interfere with the existing debug workflow. (In reply to comment #8) > Maybe I spoke too soon as this functionality "works" only if invoke the > application with debug mode. If you simply run the application the breadcrumb > mode does not automatically select the current running context. > > Maybe the solution is to have the console window support its own restart > mechanism. A restart button next to the stop button would be nice. Also a > keybinding to restart the active console would solve this problem and not > interfere with the existing debug workflow. I've always felt that the console is poorly connected to the debug view. Perhaps we should investigate whether to make the console itself be a debug context provider, then look into whether it can also drive the selection in Debug view. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |