| Summary: | [Decorators] [WorkingSets] New working set dialog triggers refresh of decorators in Package Explorer | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Nick Edgar <n.a.edgar> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse |
| Version: | 3.2 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | stalebug | ||
|
Description
Nick Edgar
This may be a JDT issue since the Navigator view doesn't have the same problem. I wonder what the trigger is though. They may have a working set manager listener that refreshes the tree in the event that a new working set is created. Something like this would be needed if they were showing working sets as top level elements. Has the working set already been created at this point? I hadn't even entered a name yet. Mmmm. I shouldn't have been but if you access a specific type for the first time the working set updater will be loaded and an event will be fired for that. The refresh happens each time, not just the first time in the session. I'm stumped! Oleg is now responsible for watching the [Decorators] category. 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. 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |