Bug 545412 - Unable to step through code with keyboard after hitting breakpoint and switch to debug perspective
Summary: Unable to step through code with keyboard after hitting breakpoint and switch...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.10   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-14 11:06 EDT by Martijn Dashorst CLA
Modified: 2023-03-01 12:44 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martijn Dashorst CLA 2019-03-14 11:06:19 EDT
When in the Java perspective the program hits a breakpoint, Eclipse switches to the debug perspective, opens the file with the breakpoint and shows the debug view. However it is impossible to use the keyboard shortcuts associated with the debugger to step through the code, but you have to explicitly select the method in the debug view using the mouse pointer in order to be able to step through the code.

This is cumbersome because:

- remove hand from keyboard
- reach the mouse
- find the pointer on the screen (on 4K and 2 monitors) that is not easy
- move pointer to debug view
- scroll debug view to top
- move pointer to top method
- click on top method

This fails consistently on macOS since forever. This might be related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=43456, however I find the reasoning not quite up-to-par in that issue. The perspective is changed, the editor is changed, so the focus *should* move to a place where the debug keybindings become active.
Comment 1 Sarika Sinha CLA 2019-03-14 13:05:36 EDT
@Seimon,
I thought this was fixed ?
Comment 2 Eclipse Genie CLA 2021-03-04 09:04:16 EST
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.

--
The automated Eclipse Genie.
Comment 3 Martijn Dashorst CLA 2021-03-08 04:48:19 EST
This problem hasn't been fixed, and is prevalent on mac OS and Linux. It is still an issue with Eclipse 2020.12.
Comment 4 Eclipse Genie CLA 2023-03-01 12:44:17 EST
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.

--
The automated Eclipse Genie.