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

[Michael Godfrey]

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

Rik,

Thanks for thinking about this.  I have tried quite
a number of experiments using pause(). Including placing
a pause() at line 412 as you suggested. Somewhat to
my surprise this pause() and pause() immediately 
before the print() in my code does not in general help.  

What seems to be mor reliable is to place pause(n) 
statements between the sequences of plot() commands.
It appears to be the case that if a long sequence of plot()
commands with hold on are given, the system gets into
a state such that it never reaches a correct state for
printing.
(Even though the dispalyed plot is correct!)

A key part of this problem, I think, is the current
requirement that the figure has to be rendered in order
for print() to work.  It is obvious that Matlab has found
a way around this even though they appear to use OpenGL.
In Matlab you can move the figure to anywhere on the screen
and then do a print().  The figure does not move as a result.
In Octave, if you move the figure, it then is moved back to 
an "original" position when print() is done. It is also
resized.

Also, John pointed out that pause() waiting at the command
line prevents callbacks from being processed.  Thus, there
does not seem to be a reliable way of "waiting" without
inhibiting actions that you are waiting for,

My lack of detailed knowledge of OpenGL and FLTK does not
help in this case.  Sorry.



    _______________________________________________________

Reply to this item at:

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

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