[Top][All Lists]

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

[Octave-bug-tracker] [bug #36679] Timing error for multiple plots

From: Michael Godfrey
Subject: [Octave-bug-tracker] [bug #36679] Timing error for multiple plots
Date: Mon, 02 Jul 2012 20:39:22 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1

Follow-up Comment #13, bug #36679 (project octave):

I tried replacing the __request_drawnow__ with
Since the __request is within a case statement
this results in many fewer calls to drawnow
than having the drawnow() unconditionally called.
(In my cae there are 11 calls to newplot() for
each pass through the top loop, but ony one
is a case "replace" which leads to drawnow()
being called.)  However, the good news is that
this fixes the problem.  This also narrows the
scope for searching for the real cause of this 

So, I am definitely in favor of changing line 58 of 
newplot() to drawnow();

I did previously try putting a drawnow() at line
412 of print.m but it did not help.  Also, tried
the usual pause()'s.

So, Rik, could you make the patch to newplot()?
This may not be a complete solution, but it will help
a lot. And, it is separate from other problems with
getting print() to be better behaved.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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