Bug 115934 - [Commands] request: Tree expand/collapse keys
Summary: [Commands] request: Tree expand/collapse keys
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-11-10 18:50 EST by Zorzella Mising name CLA
Modified: 2019-09-06 15:31 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zorzella Mising name CLA 2005-11-10 18:50:38 EST
To navigate a tree (say package explorer, or Search results) under Linux, the up
and down keys work as expected, but the left and right keys do not
expand/collapse the current node, as they do in Windows. Instead, one is forced
to use the Num Keypad "+" and "-" keys, which are by far not as convenient.

Zorzella
Comment 1 Billy Biggs CLA 2005-11-11 09:27:38 EST
You can also often toggle the expandsion state of a node by hitting the spacebar.

These are the standard GTK+ keys for a GtkTreeView, and not something that
is controlled by SWT.  If you disagree with the GTK+ keybindings, feel free to file
a bug at http://bugzilla.gnome.org/  against "gtk+".

Sorry.
Comment 2 Zorzella Mising name CLA 2005-11-11 14:40:09 EST
I was afraid you'd say that. Since keybindings in Eclipse are customizable,
isn't it possible to allow for single -- and multiple -- node expansion/collapse
in a tree to also be customizable actions? 

Right now, I can customize the keys for Expand/Collapse/Expand All/Collapse All
in the Editor, but not in the Search or Package Explorer (even if I change the
scope to "In Windows", it does not work). In fact, there is *no* keybinding for
the Expand All/Collape All actions.

Any reason to not be consistent?

Zorzella 
Comment 3 Billy Biggs CLA 2005-11-11 23:36:37 EST
Note that on GTK+, there are native key bindings for expand all (and I
think collapse all), try keypad-* and shift-left/right (however, in some
cases these are currently disabled, see bug 96892).

That all said, what Eclipse does on top of SWT is a different problem.  I'd
suggest filing a bug against Platform > UI if you think the keybindings
in Eclipse can be improved, or I guess we can move this bug there.

What exactly would you propose in Eclipse?
Comment 4 Zorzella Mising name CLA 2005-11-12 02:38:21 EST
Note that I actually did originally file this bug against UI. Moving it back, if
appropriate, is totally fine with me.

What I propose is just as I described: have the expand/collapse keybindings be
consistent -- across platforms (Win/Linux/Mac) and across parts of the product
(Editor/Search/Navigator/Package Explorer), and also be configurable, like
everything else.

I really don't know why we should be held hostage to the native keybindings --
i.e. deprive ourselves of the option of doing what is useful/consistent just to
blindly abide by defaults and prevent users from changing.

Zorzella
Comment 5 Billy Biggs CLA 2005-11-12 11:08:10 EST
Well, I think it's important to be consistent with the native applications on
the platform.
Comment 6 Billy Biggs CLA 2005-11-12 11:08:37 EST
Moving to UI.
Comment 7 Michael Van Meekeren CLA 2006-04-21 13:22:07 EDT
Moving Dougs bugs
Comment 8 Paul Webster CLA 2006-09-28 11:01:26 EDT
There are currently no plans to work on this feature.

PW
Comment 9 Denis Roy CLA 2007-06-22 09:33:09 EDT
Changes requested on bug 193523
Comment 10 Eclipse Webmaster CLA 2019-09-06 15:31:38 EDT
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.