[Octave-bug-tracker] [bug #57651] Second print command results in different marker size

[Rik]

Follow-up Comment #10, bug #57651 (project octave):

I remember trying to debug slow performance in the graphics engine several
years ago and one of the big items was that the default values set up for
graphics objects like axes were not quite correct.  This led the various
listeners to fire and start an iterative process to determine the true size of
the object.  Often the true size would be only 1 or 2 pixels different from
the default size, but it would cost 100 milliseconds processor time to get to
the true value.  It would be great for Octave's performance if we could
prevent that cycle from happening.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57651>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/