Summary: | [Dialogs] Open Resource dialog should not show non-resource working sets | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Eugene Kuleshov <ekuleshov> |
Component: | IDE | Assignee: | Platform UI Triaged <platform-ui-triaged> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | mik.kersten, steffen.pingel |
Version: | 3.3 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: | |||
Bug Depends on: | 193047 | ||
Bug Blocks: |
Description
Eugene Kuleshov
2007-05-24 02:56:13 EDT
Is there are chance that this issue will be addressed for 3.3 release (Europa)? Also note that the same issue can be reproduced using Breakpont working sets contributed by Platform/Debug (or JDT). So, Open Resource dialog finds nothing if Window working set has Breakpont working set selected. This problem in the description turned out to be that the Mylyn TaskWorkingSetPage.performFinish() was adding all adaptables instead those matching AbstractTaskContainer (bug 189308). This was effectively making the task working sets function like resource working sets that contained no resources. So if a particular facility (e.g. Open Resource, Package Explorer) had no other resource working sets selected it would not show any resources. I made a mistake in the diagnosis described in comment#2. I had nothing in the Breakpoint working set that I was testing this with, and the Open Resource dialog's working set filtering mechanism has a special case that if the only working set is empty it will set the working set to filter on to be null instead of the Window Working Set. I created bug 193047 to desribe the root problem and steps to reproduce. Reopening this bug open because it might make sense to make a fix or work-around for the Open. Reassigning to Susan. 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. |