Community
Participate
Working Groups
Build Identifier: Helios release 20100617-1415 Sometimes focus on methods gets lost and I can't travel through the code by pressing CTRL and clicking the mouse buttons until I restart Eclipse. Reproducible: Couldn't Reproduce
Sebastian, thanks for reporting the issue. In order to investigate the problem, we'd need to have some reproducible test case or scenario. Since you couldn't reproduce it right now, I intend to close this as WORKSFORME. If at any point of time you get the same problem and you can describe how it happened (testcase /stacktrace, etc), please reopen this bug. Thanks!
Someone gave some more info on bug 319933 but that's in the C/C++ editor.
Likely an issue in Platform/UI as it looks like a key mapping is lost. Move to Platform/UI
Olivier, How is the keybinding for Ctrl click defined? I suspect it might be a jdt-ui specific bug rather than platform ui.
> How is the keybinding for Ctrl click defined? There is no key binding for that. I assume this is about the hyperlink feature in editors (Ctrl + mouse move + button click). Sorry, nothing we can do without further details, please also see http://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm
The same thing happening in my eclipse instalation: Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705 WindowsXP with SP3 Sometimes Ctrl+Click just stop working in given editor. In other opened editors it just works fine. When I reopen the "broken" editor, it also works fine again. It is realy annoying. Other people in our company also noticed this behaviour. I can provide a memory dump taken when the problem occured, if that could help. Quick analisys of this dump shows, that there are two instances of CompilationUnitEditor for the same .java file (I don't know if it is a problem - just thought it might be some trace). If you think this dump might be helpful, just let me know, how to post it (it is 44M after packing it to zip, so I think I can't just add it as an attachement).
> If you think this dump might be helpful, just let me know, how to post it (it > is 44M after packing it to zip, so I think I can't just add it as an > attachement). I don't need a dump but steps to reproduce the problem.
