Bug 109143 - [WorkingSets] allow all windows to share same set of working sets
Summary: [WorkingSets] allow all windows to share same set of working sets
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-09-09 09:04 EDT by Kim Horne CLA
Modified: 2019-09-06 16:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kim Horne CLA 2005-09-09 09:04:31 EDT
There should be a preference related to the new window-level working set support that ensures that the 
working set selection for all windows remains in synch.
Comment 1 Eric Rizzo CLA 2005-09-09 09:43:48 EDT
Does "all windows" mean all Workbench windows in synch with each other, or all
Views in synch with each other.
I don't think anyone is asking for the former, but we've been asking for the latter.
See bug #45212
Comment 2 Kim Horne CLA 2005-09-09 09:55:12 EDT
Right now you have the ability for the later, but we also want to give the option for the former (as Randy 
requested) for people that use many windows.
Comment 3 Randy Hudson CLA 2005-09-09 11:34:33 EDT
Multiple windows should be treated the same as multiple perspectives in the 
same window. I don't think anyone is looking for workingset/per 
workbenchwindow. WorkingSet/per workbench is all we need, whether you have 
multiple windows or multiple perspectives open.
Comment 4 Kim Horne CLA 2005-09-09 11:39:30 EDT
I disagree.    For instance, I work with HTML and Java.  In one window is set up to use Java, the other 
HTML.  I would want a different working set for each.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:11:23 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.