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

[Rik]

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

Responding in the order of the original comments:

1) reset () is broken for plots and doesn't actually reset all of the
properties to their defaults.  There is already a bug report filed on that. 
However, I have never had a problem if I actually use 'close all' to shut down
everything associated with the plotting engine.

2) newplot is called by everything but line(); so there is a possible bypass
route around any drawnow put in newplot()

3) I agree that we still don't have a clear understanding of this bug.  If it
is related to callbacks, then putting drawnow() in the appropriate location
should fix it.

4) In newplot there is a call to __request_drawnow__ which sets a variable
that asks Octave to run drawnow the next time the user hits a prompt.  This is
only a request, and it is possible that when running from a script several
plots are done in a row before the user is returned to a prompt and drawnow is
executed.  What happens if you replace line 58 of newplot.m with a straight
call to drawnow () rather than to __request_drawnow__?

5) You may have done this in previous tests, but what happens if you put a
drawnow () call just ahead of line 412 in print.m?  There is already a call to
drawnow () at the head of print.m but it is before a lot of properties have
been altered.  I'm thinking a second call might be necessary.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36679>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/