Community
Participate
Working Groups
I rarely use double-click as the way to expand and collapse a tree node, since I can do it faster with the keyboard or single-click. How about letting the user assign double-click as "go into", or CTRL+Double-Click. To prevent SWT from also expanding the treeitem, set doit==false on the event.
No plans for this. Of course if you can convince the navigator to do so (and have platform offer the configuration option) we will do so too.
moving to UI
request for double-click gesture interpreted as "go into", for things that can't be opened, e.g., folders.
Michael, if this is already supported in the Common Navigator, please send it back this way. PW
Go Into support is not provided in the Common Navigator Framework (CNF) for 3.2. This may be considered for 3.3, at which point we can discuss whether it makes sense to provide the option.
I think we all agree it makes sense. "Go into" is a nice feature that is hard to use. There exist several other metaphors for invoking similar behavior that could be employed here: In windows, double-click is the common gesture for "go into". Any time you open a folder, if it contains a folder, double-clicking will go into it (or open it depending on prefs). In the java editor, holding down CTRL enables a hyperlink mode such that a single click performs "go into" for that token, be it a Type, Method, etc. Double-click or CTRL+DOUBLE_CLICK might be the best choice as it wouldn't interfere too much with existing tree interactions.
Ok, Go Into is now in the Project Explorer as of 3.5. So there should be some way to bind a double click to a "Go into" instead of an expand? I'm not sure about the command binding support or how this might be configured. Paul, can you help here?
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.
