Bugzilla – Full Text Bug Listing
| Summary: | [Markers] Lazy creation of Tasks View causes lost selection notification | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Randy Hudson <hudsonr> |
| Component: | IDE | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | helpwanted |
| Version: | 2.1 | ||
| Target Milestone: | 3.4 M4 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 162505 | ||
| Bug Blocks: | |||
|
Description
Randy Hudson
This is sort of related. Update: In M3, let's assume: 1) you've hacked the Tasks View to filter ON_SELECTED_RESOURCE_AND_CHILDREN, because ON_ANY_RESOURCE is not productive. 2) You press F4 and open a new workbench window on a CU, and the Tasks View is present in the Hierarchy Perspective which appears. Then: You will see the Tasks View quickly populate itself with *ALL* tasks (because it has received NULL as selection?), and then it will immediately receive the CU as the selection, and then populate itself again based on the few tasks in the CU. So, in short, it should know about the selection at the time it first populates itself, so it doesn't waste time showing you all tasts. This is probably a significant portion of the time required to open the window. Still broken in 3.0 RC2, and it affects both Problems and Tasks View. I selected on a project with Red Xs, then I selected on the Problems View which was not yet visible. I saw no items in the prob. view even though there should obviously be errors displayed. Another scenario, select a project in some view, and then open the problems view (previously closed). It should be seeded with the project as the selection. We now show a "Pending" notification as we calaculate The problem is what gets displayed, not when. It's great that displaying the wrong info is now done on a background thread. Very odd... I tried the following steps with 3.3 (on Mac OS X): - Starting with a stack containing Javadoc, Declaration, Problems and Tasks views - Set Problems and Tasks to filter on selected element and children - Bring the Declaration view to the front - Shutdown and Restart - Select a resource that will show both warnings and tasks -- I picked the org.eclipse.core.commands project - Click on Problems; notice that the warnings *are* displayed properly - Click on Tasks; notice that tasks are not shown - Click on the resource again; notice that the tasks are shown The strange thing is, if you swap the order of when you click on the Problems and Tasks views, you will see that the Tasks view is filled in properly, but the Problems view is not. I'd like to make sure we at least understand why we are getting the above strangeness. Raising the priority. Something to look at for a markers view rework This is not an issue with the new markers view. I am going to mark this for 3.4 and retest when we make the move to the new one (M4). Marking fixed as the new view has been released for M4. Verified in I20071210-0930 |