Bug 268160 - [CommonNavigator] Project Explorer should open Select Working Set dialog when switching top level to working sets
Summary: [CommonNavigator] Project Explorer should open Select Working Set dialog when...
Status: NEW
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:
URL:
Whiteboard: workingSet
Keywords: usability
Depends on:
Blocks:
 
Reported: 2009-03-11 13:34 EDT by Boris Bokowski CLA
Modified: 2019-09-06 16:18 EDT (History)
1 user (show)

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:34:48 EDT 
Select Top Level Elements > Working Sets from the view menu of the Project Explorer.

Expected: Working Sets at the top level
Actual: Projects at the top level, because "No Working Set" was selected in the Select Working Set dialog.

If no working set will be shown after switching top level elements to Working Sets, we should open the Select Working Set dialog.

Is "No Working Set" the current default? The default should probably be "Window Working Sets".
Comment 1 Dani Megert CLA 2009-03-17 03:55:56 EDT 
Francis, there were already many bugs (check bugzilla) about this i.e. that switching to Working Sets does nothing if there's no active working set. I think once bug 266030 is fixed we should attack this one.
Comment 2 Francis Upton IV CLA 2009-03-17 04:08:58 EDT 
(In reply to comment #1)
> Francis, there were already many bugs (check bugzilla) about this i.e. that
> switching to Working Sets does nothing if there's no active working set. I
> think once bug 266030 is fixed we should attack this one.
> 
+1
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:18: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.