Bug 131575 - [CommonNavigator] Problem with set selection for parents that do not define all children
Summary: [CommonNavigator] Problem with set selection for parents that do not define a...
Status: RESOLVED DUPLICATE of bug 212389
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
: 99739 129718 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-13 13:50 EST by Steve Francisco CLA
Modified: 2008-08-25 17:33 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Francisco CLA 2006-03-13 13:50:41 EST 
Projects are not being selected if the working set is not expanded in project explorer. This impacts the project creation wizards that select and reval the new project or model in the Project Explorer
Comment 1 Michael D. Elder CLA 2006-03-13 13:52:57 EST 
The issue here is that the working set extension from WTP 1.0 does not define all of its possible children (which could be anything). The solution for the next incarnation of the working set extension must handle this correctly. One possibility is for the working set extension to indicate that it can return the parent for _any_ element; since a working set could contain just about anything.
Comment 2 Michael D. Elder CLA 2006-03-29 16:12:47 EST 
*** Bug 99739 has been marked as a duplicate of this bug. ***
Comment 3 John Lanuti CLA 2006-03-29 16:25:08 EST 
*** Bug 129718 has been marked as a duplicate of this bug. ***
Comment 4 Michael D. Elder CLA 2006-05-04 10:49:16 EDT 
Working Sets for the Common Navigator are not supported by the Platform for 3.2.
Comment 5 Michael D. Elder CLA 2006-07-13 11:08:35 EDT 
We'll take another look at this issue in 3.3 to see if there's a way that the CNF could identify which extensions are interested without knowing their complete set of possibleChildren.
Comment 6 Michael D. Elder CLA 2007-03-26 08:59:06 EDT 
Without significant reason, this will not be addressed in 3.3
Comment 7 Mike Wilson CLA 2008-06-09 10:12:14 EDT 
... nor in 3.4, apparently.
Comment 8 Francis Upton IV CLA 2008-08-17 18:38:14 EDT 
This might be fixed by bug 212389.  When that is checked in (for 3.4.1/35M2) we should see if this can be reproduced.  It should be checked in in a day or so.
Comment 9 Francis Upton IV CLA 2008-08-20 03:18:26 EDT 
Can you provide the exact steps to make this happen?

I created a workspace with a project and set the top-level display to show workspaces, and had the workspace not expanded, then I selected link with editor, and selected and editor in that project and the selection worked fine.

I don't know how to get a selection to happen on a project node.

Please be sure and try this only with a 3.4.1 build after M20080820-0800, or a 3.5 build after N20080819 as there have been fixes that might affect this.
Comment 10 Francis Upton IV CLA 2008-08-25 17:33:47 EDT 
I was not able to reproduce this after the fix to bug 212389.

*** This bug has been marked as a duplicate of bug 212389 ***