Bug 84320 - [WorkingSets] keep only working set projects open.
Summary: [WorkingSets] keep only working set projects open.
Status: RESOLVED DUPLICATE of bug 58085
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kim Horne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-03 07:14 EST by Nikolay Metchev CLA
Modified: 2007-06-21 16:10 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Metchev CLA 2005-02-03 07:14:49 EST
At the moment I have many projects and I have grouped them all into various
working sets. Some projects overlap in many working sets. I want to be able to
go from one working set to another and be sure that all projects outside of my
working set are closed. There are 2 possible ways this could be achieved.
1. When switching working sets have the option of keeping any overlapped
projects open and closing any open projects outside of the new working set.
2. Provide a button somewhere that says - close all projects outside of
currently selected working set.
Comment 1 Noel Grandin CLA 2005-07-25 08:13:04 EDT
This is my opinion of how this should be implemented :-)

In the package explorer, when using working sets, I would like to see 2 more
entries in the context menu:
Close All Projects - closes all projects in the selected working set
Open All Projects - opens all projects in the selected working set

These 2 entries should be usable if multiple working sets are selected and the
context menu activated.
Comment 2 Benjamin Muskalla CLA 2006-08-14 16:29:04 EDT
I think the best way is to set this in the user preferences. I think there are many developers switching between working sets often and opening/closing projects every time eats too many resources.
Comment 3 Kim Horne CLA 2007-06-21 16:10:37 EDT

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