Community
Participate
Working Groups
I have a bunch of projects (~50 or so) and 2 working sets set to match 4 of them. When selecting top level workingset in package explorer it will let me select which working set to use. In project explorer I'm not asked and the top level is not changed - its as if no working set existed. I believe this is a regression from previous versions and since project explorer is the only one supporting nested projects too i'm marking this critical.
Is this really a regression? How does the same scenario behave with Luna? My guess is that it's not a bug, but more the fact that if you have no workingset enabled (via "Select Working Sets..."), then the project explorer fails back to showing all projects. I understand the UI is not optimal, and automatically opening the window to select working sets when none is available and switching to workingsets as top-level elements is a good idea. I'm marking this as an enhancement request and re-titling this report to make it clearer what's the current state and what's user expectation.
well if its not a regression than its a major reason to not use Project Explorer :) With package explorer it shows all my workingsets including "Other" for the things not in a working set. in project explorer I seem to *only* be shown things in the workingset, so its really not a good UX at all even if I was shown the select working set dialog.
(In reply to Max Rydahl Andersen from comment #2) > in project explorer I seem to *only* be shown things in the workingset, so > its really not a good UX at all even if I was shown the select working set > dialog. There are 2 things provided by working sets in Project Explorer: organization and filtering. When enabling some working set (from "Select Working Set"), then you are configuring filters. Only the content of the selected Working Sets is shown. When setting top-level element as "Working Sets", then you are configuring organization. Top-level element become the selected working sets. What you describe seems to be that you have selected some working sets, but not made top-level elements to be working sets.
No, I have selected all workingsets and enabled the toplevel working sets. I now only shows the workingsets - what is called Other in Package Explorer just dont seem to exist. So I'm back to using package explorer as I do not want to be forced to categorize *everything* in workingsets.
See bug 266030 for a default working set. I made a patch for it, I think it would help if you could review it and add a vote. So it this bug a dup of 266030 ?
this does look like a duplicate - unfortunately I can't try the patch since its not applying cleanly ;/ can you rebase it ?
