|
| Re: overriding property handling globally [message #126278 is a reply to message #126264] |
Thu, 15 June 2006 20:38   |
Eclipse User |
|
|
|
Originally posted by: jefmyers.us.ibm.com
Ernest,
If your widgets have a common base class with the model property, you
should be able to specify the property editor in an override on that
class, then override the override on subclasses when necessary.
Hope this helps,
- Jeff
|
|
|
| Re: overriding property handling globally [message #126326 is a reply to message #126278] |
Fri, 16 June 2006 13:17 |
 Ernest Pasour
Messages: 65
Registered: July 2009 |
Member |
|
|
Jeff,
What I really want to do is to allow my users to assign the model
property of arbitrary widgets (if I have a connection that can be made).
So if they've dropped a JList, I want to discover that and allow them
to select from any data sources that I know about that are adaptable to
a ListModel. However, if the argument to setModel is not relevant to
me, then I would just let the default property editing take place.
What I have kind of working at the moment is a context menu item that
gets added to widgets. When the user invokes the context menu for a
JList object, I decide what sort of hookup (if any) is available.
I'm just trying to see if it's possible to get that same behavior in the
property sheet.
Thanks,
-Ernest
Jeff Myers wrote:
> Ernest,
>
> If your widgets have a common base class with the model property, you
> should be able to specify the property editor in an override on that
> class, then override the override on subclasses when necessary.
>
> Hope this helps,
> - Jeff
|
|
|
|
| Re: overriding property handling globally [message #613357 is a reply to message #126278] |
Fri, 16 June 2006 13:17 |
Ernest Pasour
Messages: 65
Registered: July 2009 |
Member |
|
|
Jeff,
What I really want to do is to allow my users to assign the model
property of arbitrary widgets (if I have a connection that can be made).
So if they've dropped a JList, I want to discover that and allow them
to select from any data sources that I know about that are adaptable to
a ListModel. However, if the argument to setModel is not relevant to
me, then I would just let the default property editing take place.
What I have kind of working at the moment is a context menu item that
gets added to widgets. When the user invokes the context menu for a
JList object, I decide what sort of hookup (if any) is available.
I'm just trying to see if it's possible to get that same behavior in the
property sheet.
Thanks,
-Ernest
Jeff Myers wrote:
> Ernest,
>
> If your widgets have a common base class with the model property, you
> should be able to specify the property editor in an override on that
> class, then override the override on subclasses when necessary.
>
> Hope this helps,
> - Jeff
|
|
|
Powered by
FUDForum. Page generated in 0.03033 seconds
] 
Search
Help
Register
Login
Home
