octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Graphics properties implementation


From: Shai Ayal
Subject: Re: Graphics properties implementation
Date: Sat, 12 Jan 2008 19:25:11 +0200

While we are on the subject -- How about documentation for the
properties? Maybe you have some idea on how to incorporate it into the
BEGIN/END block?

Shai

On Jan 12, 2008 7:15 PM, Michael Goffioul <address@hidden> wrote:
> On 1/12/08, John W. Eaton <address@hidden> wrote:
>
> > On 12-Jan-2008, Michael Goffioul wrote:
> >
> > | Related to hidden properties, I think that properties like
> > | __plot_stream__ and so on should be hidden. Normally, hidden
> > | properties should not be listed by the "get(void)" method; they
> > | should only be accessible on explicit requests by the
> > | "get(caseless_str)" method. However, doing this will make
> > | some m-code not functional: for instance, "drawnow" uses
> > | "get(fig_handle)" to get a structure containing all properties;
> > | if hidden properties are not part of the structure, drawnow
> > | will fail. What do you think?
> >
> > Instead of
> >
> >  get (void)
> >
> > how about defining the function as
> >
> >  get (bool all = false)
> >
> > ?  If ALL is TRUE, it would return all properties, including those
> > that are hidden.  Then, for the gnuplot backend, we could define an
> > internal __get__ function that passes TRUE to the C++ get function.
>
> Looks fine for me.
>
> Michael.
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]