Bug 116213 - [WorkingSets] Working sets should support opened windows persistence
Summary: [WorkingSets] Working sets should support opened windows persistence
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-14 06:23 EST by Martin Novák CLA
Modified: 2019-09-06 16:03 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 Martin Novák CLA 2005-11-14 06:23:29 EST
Hi, I don't know whether it's included in the remake of working sets plan, but
huge usability improvement would be to support automatic persistence which
windows has been opened in which working set. I explain why: Most of the
developers are working on one or more projects at the same time as I do. I'm
working some of the days in a week on the first one, and then on the second one.
I also use working sets to filter package navigator. But I would appretiate when
I switch between working sets, to have workspace (opened editor windows) at the
same status as it was in the previous session. It would help me to see which
files has been opened, and I can dive to the problem without thinking where did
I end last time.
Comment 1 Kim Horne CLA 2005-11-14 10:23:49 EST
I'm not sure I understand.  You want it such that when you change the window working set that your 
selection of opened editors will change to match what editors were open last time that working set was 
chosen?
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:03:39 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.