Re: Graphics properties implementation

[John W. Eaton]

On 13-Jan-2008, Shai Ayal wrote:

| On Jan 13, 2008 1:31 AM, Michael Goffioul <address@hidden> wrote:
| > On 1/12/08, Shai Ayal <address@hidden> wrote:
| > > with the help of Ben's excellent property list
| >
| > Good reference indeed, thanks.
| >
| > >I am attaching a patch
| > > to add properties to base_property. The added properties:
| > >  radio_property busyaction;
| > >  callback_property buttondownfcn;
| > >  bool_property clipping;
| > >  callback_property createfcn;
| > >  callback_property deletefcn;
| > >  radio_property handlevisibility;
| > >  bool_property hittest;
| > >  bool_property interruptible;
| > >  bool_property selected;
| > >  bool_property selectionhighlight;
| > >  callback_property uicontextmenu;
| >
| > I think this one should be a handle_property to hold a handle
| > to a to-de-defined menu object.
| >
| > >  array_property userdata;
| >
| > I think this one should be a any_property, because it can
| > be anything.
| >
| > >  bool_property visible;
| > >
| > > Note:
| > > (1) the visible property had a special set method in figure which is
| > > overwritten in this patch. Making base_property::set_visible virtual
| > > solves this problem. Do you think this should be done for all
| > > base_property::set functions?
| >
| > Another possibility would be to have listeners in C++, I'm thinking
| > about a possible solution, but I think it will be slower than making
| > the set_xxx methods virtual in base_properties class. For the
| > moment, I would only set set_visible virtual, because I can't think
| > about a potential use case for the other properties.
| >
| > > (2) I am not sure about the type of the uicontextmenu property
| >
| >
| 
| Corrected patch attached
| 
| 
| 2007-21-01 Shai Ayal <address@hidden>
| 
|    * graphics.h.in (base_property): add properties to base_property

I applied this patch and checked it in.

Thanks,

jwe