Community
Participate
Working Groups
Normally in the Debug perspective after stopping at a breakpoint and editing the source file, an incremental recompile occurs and the debugger rewinds typically to the first line of the current function. Good. This can be very irritating if the edit is still in progress and the context for the continuing edit is corrupted (and of cpurse the debgger tries to load a heap of compilation errors). There is however a plausible conflict between the editor as a debug output medium and a user input medium. Bad ergonomics but not necessarily a bug. However if the user has changed to a normal Java perspective, there is no conflict, the editor is there to support Java editing. Anything that corrupts the user's editing actions is a BUG. When the Debug view is not visible, the debugger updates should be suspended. a) No repositioning of editors should occur b) Probably no incremental reloading should occur either. To avoid the bad ergonomics, when the Debug View is visible, a debug update can occur if the Debug or Variables View has focus, but never while the editor has focus.
If someone can spend some time to look into this, I can guide/review.
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.
Definitely not stale. Although this could be regarded as one of a plethora of near-duplicate bugs open on the debugger's focus / inactive state handling.
