Graphics properties implementation

Shai Ayal shaiay at gmail.com
Mon Jan 14 23:18:22 CST 2008


On Jan 13, 2008 8:47 AM, John W. Eaton <jwe at bevo.che.wisc.edu> wrote:
>
> On 13-Jan-2008, Shai Ayal wrote:
>
> | On Jan 13, 2008 1:31 AM, Michael Goffioul <michael.goffioul at gmail.com> wrote:
> | > On 1/12/08, Shai Ayal <shaiay at gmail.com> 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 <shaiay at users.sourceforge.net>
> |
> |    * graphics.h.in (base_property): add properties to base_property
>
> I applied this patch and checked it in.
>
> Thanks,
>
> jwe
>

I attache a patch to add properties to the line and text objects.
Notes:
(1) line has (historically) the ldata, udata, xldata, xudata,
keylabel, interpreter properties whic are not matlab compatible. I
think keylabel is called displayname in matlab. The others I'm not
sure about
(2) I did not add the dynamic data properties xdatamode and x/y/zdatasource

Shai

2008-01-15 Shai Ayal <shaiay at users.sourceforge.net>

    * graphics.h.in (line): added displayname, erasemode properties
     (text) added backgroundcolor, displayname, edgecolor,  erase_mode
, editing, fontunits, linestyle, linewidth, margin, verticalalignment
properties
-------------- next part --------------
A non-text attachment was scrubbed...
Name: add_line_text_property.patch
Type: text/x-patch
Size: 1328 bytes
Desc: not available
Url : https://www.cae.wisc.edu/pipermail/octave-maintainers/attachments/20080115/0bf9f7a9/attachment.bin 


More information about the Octave-maintainers mailing list