Bugzilla – Full Text Bug Listing
| Summary: | [WorkingSets] Window Working Set is not in LRU | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dani Megert <daniel_megert> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dirk_baeumer |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Dani Megert
This is a problem in Platform/UI. We add the window working set to the LRU list of the working set manager, however the manager itself ignores the window working set. Having an MRU list for working sets at the workbench level was a really poor idea. Guh. So much about the working set API bugs me. Anyhoo, the rationale for this filtering - some working sets (ie: the window set) only make sets in certain contexts (ie: the window they're hosted in). Imagine having two windows, each with their own working set. You could start seeing two "Window Working Set" entries in the same MRU list with no reasonable way to discern between them. I was considering hardcoding the Window Working Set into the WorkingSetFilterActionGroup which would fix it for our clients but you'd need to do the same thing for your implementation unless you've decided to migrate to ours... 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. |