Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354969

Summary: Extension Element Details not updated after selection change
Product: [Eclipse Project] PDE Reporter: David Huber <david>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: minor    
Priority: P3 CC: curtis.windatt.public
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description David Huber CLA 2011-08-17 11:34:56 EDT 
Build Identifier: 20110615-0604

The "Extension Element Details" form of the plugin's extension tab is not updated correctly when changing from a multiple selection in "All Extensions" to a single selection. The new selection must be for one of the elements of the multiple selection.
Selecting an item that was not part of the multiple selection will update the form correctly.

Reproducible: Always

Steps to Reproduce:
1. Create a plugin project (no UI contrib, no Activator, no Wizard)
2. Add dependency to org.eclipse.core.runtime
3. Add the "org.eclipse.core.contenttype.contentType" extension point in the "Extensions" tab
4. Add two "content-type" to it
5. Select both of them (fields on the right should all be blank now)
6. Without deselecting first, click on the second item (Fields stay blank!)
Comment 1 Curtis Windatt CLA 2011-08-18 15:22:44 EDT 
This is a good find, do you have time to look into contributing a patch?
Comment 2 David Huber CLA 2011-08-19 04:12:37 EDT 
(In reply to comment #1)
> This is a good find, do you have time to look into contributing a patch?

I dug a little deeper into the problem and found that it is actually not PDE related, sorry for that. 
It looks like the problem is with SWT trees (did not test tables and lists, but that would be info for SWT people anyway). I'm currently looking if I can find an existing BUG report about it.

Regards
David Huber
Comment 3 David Huber CLA 2011-08-19 05:48:30 EDT 

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