Comment 1 Knut Radloff 2003-02-06 12:00:50 EST

Already received the disabled icon. Should fix for RC1.

Comment 2 Nick Edgar 2003-02-07 12:45:49 EST

Actually, want to disable it when there are no top-level items (i.e. if you 
used Go Into).

Comment 3 Knut Radloff 2003-02-14 17:47:54 EST

I'd say that collapse all should be enabled as long as there is at least one 
container, regardless of whether it's expanded or not.
Is that what you had in mind? We don't want to disable it when one goes into a 
project. There could still be plenty of expanded folders.

Comment 4 Knut Radloff 2003-02-14 17:48:29 EST

Nick, please see question above.

Comment 5 Nick Edgar 2003-02-17 12:55:15 EST

If there are no items in the tree that are collapsable, then Collapse All 
should be disabled.  Don't need to track actual collapsed state (OK to leave 
enabled if all items are already collapsed).

Here are the cases where it should be disabled:
- workspace root is input but there are no projects in the workspace
- project is input but it has no folders
- folder is input but it has no subfolders

If this is tricky or can be potentially expensive to track, let's not bother.
I wouldn't spend too much time on this one.
I don't see this as critical for 2.1, so you can remove the RC1 tag if you like.

Comment 6 Nick Edgar 2003-02-19 13:47:35 EST

Defer

Comment 7 Knut Radloff 2003-09-02 17:00:54 EDT

Reassigning to Nick since he is taking ownership of Navigator

Comment 8 Eclipse Webmaster 2019-09-06 16:05:40 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.