Community
Participate
Working Groups
One of the most common operations in the eclipse is to navigate to the declaration of a variable. Currently there are two ways to do this : F3 and ctrl+left click In order to speed the execution we should be able to use the middle button. It's similiar to what is used in Firefox to open links in new tabs.
*** Bug 123097 has been marked as a duplicate of this bug. ***
See also bug 47099.
Is there any progress planned for this bug? It was open in 2005, and as of today it is still not possible to middle-click (as in IntelliJ, instead of ctrl-click) to open declaration. I know there is not many votes for the bug, but still I really think it wouldn't be hard to implement, and would be a huge UI improvement. Thanks.
>Is there any progress planned for this bug? No, as there was no work done on bug 47099. Now, if you think it is so easy to implement you are welcome to provide a good quality patch.
I'm not so sure anymore whether bug 47099 would be a good path to solve this. F3 always uses the current caret location, but middle-click should target the element under the mouse (like Ctrl+click). We should just hardcode mouse button 2 to perform the default hyperlink action in text editors.
>We should just hardcode mouse button 2 to perform the default hyperlink action >in text editors. I'm against that. But I agree that makes more sense to bind it to 'Open Hyperlink' rather than 'Open (F3)'.
We can always start using infrastructure from the platform once that's available, but until then, I think it's OK to follow the platform's example and hardcode this like: PaneFolder.mouseListener.new MouseAdapter() {...}.mouseUp(MouseEvent) Binding mouse button 2 to the 'Open Hyperlink' command alone would not be enough. It actually needs to be "click button 1 and then run 'Open Hyperlink'" or "MOD1 + click button 1".
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.
