Bug 282493

Summary:	[CommonNavigator] Opened folders are collapsed when changing working sets
Product:	[Eclipse Project] Platform	Reporter:	Peter Bakonyi-Karpati <eclipsebugzilla>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	susan
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	workingSet

Description Peter Bakonyi-Karpati

2009-07-06 04:27:31 EDT

Build ID: I20090522-1710

Steps To Reproduce:
1. Create 2 or more working sets
2. Select one of them
3. Open folders
4. Change to another working set
5. (Open folders)
6. Change back to previous working set
7. All folders are collapsed


More information:

Comment 1 Susan McCourt

2009-07-08 16:42:41 EDT

Actually, it depends on the content of the working sets.
It appears that an attempt is made to remember the expanded nodes when switching working sets, but these are only remembered per switch.  So nodes that exist in both the "before" and "after" version of the tree will remain expanded.

Examples:
If you expand nodes in working set A and then switch to no working set, the nodes in A are remembered as expanded as you switch between no working set and A.  

If you then switch to working set B and expand some nodes in B, you'll see the expansions in both working set B and no working set.

If you switch between A and B, only those nodes that exist in both working sets that are expanded will be remembered.

To fix this bug, the expansions would have to be remembered additively and remembered across multiple working set changes.

Comment 2 Hitesh

2009-07-22 09:36:32 EDT

Susan, I guess this is Project Explorer.

Comment 3 Peter Bakonyi-Karpati

2009-07-22 09:37:24 EDT

yes it is Project Explorer

Comment 4 Hitesh

2009-08-19 09:00:57 EDT

See comments #2 and #3.

Comment 5 Eclipse Webmaster

2019-09-06 16:12:20 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.