Bug 268167 - [CommonNavigator] Project Explorer does not refresh upon window working set changes
Summary: [CommonNavigator] Project Explorer does not refresh upon window working set c...
Status: RESOLVED DUPLICATE of bug 266030
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Francis Upton IV CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 13:43 EDT by Boris Bokowski CLA
Modified: 2009-04-25 10:02 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2009-03-11 13:43:30 EDT 
Steps:

1. Customize Perspective > Command Groups Availability, check "Window Working Set"
2. Window > Working Sets > Edit...
3. Uncheck all, OK
4. Open Project Explorer
5. From view menu, select Top Level Elements > Projects
6. From view menu, open Select Working Set dialog
7. Select "Window Working Set", click OK
8. From view menu, select Top Level Elements > Working Sets
9. Project Explorer still shows projects at top level (bug 268160)
10. Window > Working Sets > Edit...
11. Check all, OK

actual: projects still at top level
expected: working sets at top level

12. From view menu, open Select Working Set dialog
13. Cancel

--> now the Project Explorer refreshes and shows working sets

14. Window > Working Sets > Edit...
15. Uncheck all, OK

-> Project Explorer is empty!

16. From view menu, open Select Working Set dialog
17. Cancel

-> Project explorer at least shows projects again
Comment 1 Boris Bokowski CLA 2009-03-11 13:44:21 EDT 
Could it be that the Project Explorer does not have the "Other" pseudo working set?
Comment 2 Francis Upton IV CLA 2009-03-11 13:48:50 EDT 
(In reply to comment #1)
> Could it be that the Project Explorer does not have the "Other" pseudo working
> set?
> 

Yes, that's a known issue, there is already a bug for that.
Comment 3 Francis Upton IV CLA 2009-04-25 10:02:56 EDT 

*** This bug has been marked as a duplicate of bug 266030 ***