[Top][All Lists]

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

[Octave-bug-tracker] [bug #54551] poor auto axes limits chosen with 3-D

From: Andy Potvin
Subject: [Octave-bug-tracker] [bug #54551] poor auto axes limits chosen with 3-D patches
Date: Wed, 22 Aug 2018 13:07:45 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36

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

Thanks Dmitri for the SUPER-quick reply!

So it's NOT related to the 3-D patch.  And it's a known behavior/bug/feature. 

But see the following:
ax = gca;

In MATLAB (again R2012a) you can see the text.  In Octave you can't.  That's
an Octave bug. I.e. "Octave fails to show text when Clipping is off"

[FN1] My work around was just to set the limits manually.  FYI MATLAB (R2012a)
behavior of my example is to show the text even though it sets an auto
ZLim=[-3 -1] - so I guess that would be  MATLAB bug (as long as text clipping
is off.


Reply to this item at:


  Message sent via Savannah

reply via email to

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