octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #57040] contour does not merge axes domains, i


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57040] contour does not merge axes domains, if hold
Date: Fri, 11 Oct 2019 08:09:27 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #2, bug #57040 (project octave):

What version of Matlab?  I find it strange that calling contour causes the
axis limit modes to be set to manual.

I see a comment in the __contour__.m function that indicates that the reason
for setting the axis modes was to avoid computing axis limits repeatedly as
patches are added.  But now I'm wondering if we are doing this job incorrectly
and should instead only be computing axis limits when rendering the axes or if
explicitly requested.  For example, do the the following different in Matlab? 
Note that these commands must be executed all on one line or in a script to
avoid an implicit drawnow action when a command prompt is displayed.


clf; plot ([0, 10], [0, 10]); get (gca, {'xlim', 'ylim'})



clf; plot ([0, 10], [0, 10]); drawnow; get (gca, {'xlim', 'ylim'})


Only computing axis limits when rendering or when requested would improve
efficiency generally and avoid the need for the kind of special code that
attempts to defer computation of limits like we currently have in
__contour__.m.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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