Bug 142343 - [WorkingSets] Window Working Set doesn't get selected on working set deletion
Summary: [WorkingSets] Window Working Set doesn't get selected on working set deletion
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-17 16:36 EDT by Bogdan Gheorghe CLA
Modified: 2019-09-06 16:15 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Gheorghe CLA 2006-05-17 16:36:24 EDT
The Window Working Set doesn't always get selected when an existing working set gets deleted, resulting in missing projects in the Package Explorer.

Repro Steps:
1. Start with a workspace that has a number of Java projects.

2. Select "Select Working Set..." from the Package Explorer drop down menu

3. Create a new Java Working set and assign 1 java project to it -> Click Finish->Now hit select All to select your new working set and Click OK

4. From the Package Explorer dropdown, select Top Level Elements>Working Sets

5. Go to the dropdown menu and select "Configure Working Sets..." and delete the working set you created

6. From the dropdown select Top Level Elements>Projects -> notice how only the project that you added to the working set is displayed. This is because the "Window Working Set" does not get selected again when switching back.
Comment 1 Bogdan Gheorghe CLA 2006-05-17 16:36:50 EDT
BTW, I20060512-1600
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:33 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.