octave-maintainers
[Top][All Lists]
Advanced

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

Re: Is __modified__ graphics prop useful anymore?


From: Daniel J Sebald
Subject: Re: Is __modified__ graphics prop useful anymore?
Date: Mon, 24 Oct 2016 16:43:36 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2

On 10/24/2016 04:32 PM, Rik wrote:
On 10/24/2016 02:14 PM, John W. Eaton wrote:
On 10/24/2016 05:10 PM, John W. Eaton wrote:  >> On 10/24/2016 04:48 PM, Rik wrote: >>> 10/24/16 
>>> >>> I made the
graphics property __modified__ a hidden property >>>
(http://hg.savannah.gnu.org/hgweb/octave/rev/4ea5b0c3b10f).  But, I
can't >>> see that it is used anywhere usefully in the code.  Maybe it
had a >>> purpose >>> a long time ago, but should it just be put on the
road to deprecation >>> now? >> >> Isn't it used in
base_properties::mark_modified method?  I think the >> purpose is to tag
a set of properties as modified so that there is a >> quick way to know
whether something has changed and the object needs to >> be drawn again.
 > > The base_properties::is_modified method checks the status.  It's
used in Fdrawnow. >

But nothing seems to set the value to "off".

octave:12> hax = gca;
octave:13> get (hax, "__modified__")
ans = on
octave:14> drawnow
octave:15> get (hax, "__modified__")
ans = on

--Rik

Perhaps this is why we see plots being drawn twice quite often, possibly all toolkits, but gnuplot for sure, which would most noticeable because of its relative slowness.

Dan



reply via email to

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