| Summary: | [Tasks] Task view does not update filter correctly when a selection provider gives on items | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Chris McLaren <csmclaren> |
| Component: | UI | Assignee: | Stefan Xenos <sxenos> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 17783 | ||
|
Description
Chris McLaren
this is due to the fact task view has intentionally introduced a bug: i.e. to only change the selection when the active part is an editor, or a view providing a structured selection of one or more resources. the motivation for this i believe is to force a lazy behavior so the task view doesn't flicker too much when activating views that don't contribute to the task view. the design problem is that the task view is proactively attaches itself to the selections of the active view without any knowledge if that view can provide a meaningful selection. outline view, for instance, returns a selection of 0 items even when there is no outline available, where other views return null for their selection. without a formal contract between the task view and the active view for the active view to supply resources, the task view needs to be able to intelligently determine whether or not a selection is providing resources. it cannot do this with a null or empty selection. (ignore this comment: bugzilla test) (ignore this comment: bugzilla test 2) |