| Summary: | Type hierarchy should support working sets | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Erich Gamma <erich_gamma> |
| Component: | UI | Assignee: | Martin Aeschlimann <martinae> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | dirk_baeumer |
| Version: | 2.1 | ||
| Target Milestone: | 3.0 M6 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Erich Gamma
Is the working set used as a filter on the hierarchy, or is the working set just a more complex input of the hierarchy? In the first case the problem is that you won't see certain branches of the tree if the parent happens to be outside of the working set. E.g. in the normal hierarchy this would mean the hierarchy is empty when 'Object' is filtered. It would act as filter. The presentation would behave in the same was as when you open a type hierarchy on a package or project, i.e., base types outside of the working set are shown with a hollow type icon. *** Bug 19784 has been marked as a duplicate of this bug. *** added > 20031102 |