Bug 37084 - [Dialogs] why forcing IAdaptable object as the element
Summary: [Dialogs] why forcing IAdaptable object as the element
Status: RESOLVED DUPLICATE of bug 56212
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P4 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-30 06:11 EDT by Joseph Khalil CLA
Modified: 2004-12-06 15:21 EST (History)
1 user (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 Joseph Khalil CLA 2003-04-30 06:11:38 EDT 
i wonder why the PropertyPage  insist on making the element in it which is 
passed to the page as IAdaptable else a class cast exception occurs.
in my case the object i want to see its properties is not IAdaptable and i
don't want it to implement this interface in its class because i want the class 
to be generic and doesn't depend on eclipse,
by forcing that the element is IAdaptable you stop the user from showing his 
ordinary objects (objects that don't implement IAdaptable) in the properties 
dialog.
i know that i can wrap my object in an object that implement IAdaptable but i 
think the best way is to make the element as Object class object
Comment 1 Tod Creasey CLA 2003-05-08 11:09:42 EDT 
The IAdaptable element was selected so that support for the preference and 
property pages for elements that adapt to IResource were supported.

Marking this as a feature request as it is a breaking API change.
Comment 2 Jean-Michel Lemieux CLA 2004-12-06 15:21:38 EST 

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