Community
Participate
Working Groups
Eclipse 3.1 M1 When I press "Ctrl+End" in the java editor and then I hit the "Back" button on my mouse which is equivalent to "Alt+Left" it doesn't go back to the place where I hit "Ctrl+End" from.
navigation history seems broken
Works for me using R3.4.
*** This bug has been marked as a duplicate of bug 238202 ***
It still doesn't work for me with release R3.4. And I don't think the bug you have duplicated with is correct.
>It still doesn't work for me with release R3.4. No one claimed that ;-) >And I don't think the bug you have duplicated with is correct. It is, trust me.
>>It still doesn't work for me with release R3.4. >No one claimed that ;-) In comment 2 you claimed it works for you! :-) I assumed that this means it should work for me as well. I guess I was wrong. >>And I don't think the bug you have duplicated with is correct. >It is, trust me. It might be from a technical point of view. However I am pretty certain from the users point of view it isn't. In any event... anything you guys do to fix the problem will be greatly appriciated.
Mmh, Nikolay you are 100% right. I misread the bug. I tested the following scenario: 1. Ctrl+End 2. switch to another editor 3. go back which works but your scenario: 1. Ctrl+End 2. back doesn't. The reason is that we don't record any caret moves.
Thank you Daniel, Looking forward to the fix.
It's hard to find the right amount of caret moves to put into the history. You certainly don't want every caret move to end up in the history, otherwise the history quickly gets swamped with many little moves as soon as you e.g. start editing a method and move around with Ctrl+Left/Right or just the arrow keys. I guess we would need some new heuristics to find "interesting" locations triggered by caret moves, e.g.: - a location is interesting if the caret stayed there for a few seconds - a location is not interesting if it is very close to the previous location (e.g. within a few lines, inside the same block, when no scrolling was necessary to reveal the new location, ...)
*** Bug 241811 has been marked as a duplicate of this bug. ***
*** Bug 346669 has been marked as a duplicate of this bug. ***
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.
