[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wxt (was: Re: improved __contourc__.cc + filled contours)
From: |
Ben Abbott |
Subject: |
Re: wxt (was: Re: improved __contourc__.cc + filled contours) |
Date: |
Mon, 15 Oct 2007 14:56:47 -0700 |
On Monday, October 15, 2007, at 12:45PM, "John W. Eaton" <address@hidden> wrote:
>On 15-Oct-2007, Ben Abbott wrote:
>
>| How about
>|
>| set (0, 'terminal', 'wxt') ?
>
>At this point, I'd prefer to avoid adding properties that are not
>compatible with Matlab. A terminal property with gnuplot-specific
>names is also asking for trouble when/if we switch to some other
>plotting backend. Yes, we already have this problem with the print
>function handling lots of output formats that may be difficult to
>obtain with other graphics backends, but I'd at least like to limit
>the damage.
>
>jwe
Good points.
Is there any plan to provide the setappdata and getappdata functions from
Matlab?
They behave similarly to "get" and "set", but are intended for specific
applications ... user defined apps I suppose. Perhaps such a functionality
would allow individuals to come up with backend specific functionality without
burdening other backends or breaking matlab compatibility.
>From Matlab 7.3; "help setappdata"
SETAPPDATA Set application-defined data.
SETAPPDATA(H, NAME, VALUE) sets application-defined data for
the object with handle H. The application-defined data,
which is created if it does not already exist, is
assigned a NAME and a VALUE. VALUE may be anything.
See also getappdata, rmappdata, isappdata.
Re: [unclassified] Re: improved __contourc__.cc + filled contours, Kai Habel, 2007/10/16
Re: improved __contourc__.cc + filled contours, Kai Habel, 2007/10/16
improved __contourc__.cc + filled contours, John W. Eaton, 2007/10/19