| Summary: | [CommonNavigator] Project Explorer Working Sets As Top-Level Do Not Work | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Mark Melvin <mark.melvin> |
| Component: | UI | Assignee: | Michael D. Elder <mdelder> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Mark Melvin
1) the application name should once again be "org.eclipse.ui.ide.workbench" - there was some confusion there for awhile 2) I'm not entirely sure myself. I will forward this bug along to the right people to address this issue. 3) The third button governs the contents of the window working set. The window working set is an aggregate working set - it contains other working sets. With all views set to the window working set, this button allows you to quickly change the filter on all views to match a list of working sets. If the window working set is empty the views will act as if they are unfiltered. Can you provide a little more information about what your second question? "2) Why doesn't the default application ID contribute what I consider very useful functionality to the Project Explorer view? I very much like viewing the working sets at the top level, and didn't realize this wouldn't be exposed in 3.3 out of the box." If you select the "Select Working Set" action, then choose a check list of Working Sets, you can have the view display many working sets at the same time. If you want to show them in a group, choose "Top Level Elements> ..". You may have opened the view after you started the workbench. There was a defect that was recently fixed where the Working Set menus were displayed if the view was opened after the workbench started; could this be what you're referring to? I have tried this with the latest integration build and it seems to be working. I think what led me to confusion before is I was creating a single working set, and never seeing it in the Project Explorer - even if I set the working sets to be "top level". (note I am using the platform runtime only and the Resource perspective) It appears that the view will not show the working set at the top level if there is only a single working set selected. I guess this makes sense, it just isn't consistent with the way the Java Perspective works (and what I was used to) where it will always show a working set at the top level, even if there is only one working set present (or 'none', in which case it creates a dummy "Other Projects" working set for you - and shows it at the top level). In that case, it sounds like the real issue is the consistency. I will close this as a duplicate of bug 157877. It won't be addressed in 3.3, but I think we can address it in 3.4. *** This bug has been marked as a duplicate of bug 157877 *** |