[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: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #54551] poor auto axes limits chosen with 3-D patches
Date: Wed, 22 Aug 2018 16:51:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0

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

@Andy: I played with your example from comment #2 and there seems to be a
critical value of zlim above which Octave behaves correctly:

plot (1:10)
ht = text (5, 5, 3,'text', 'Clipping','off')
## zlim = [0 1];
zlim ([0 2]) ## Above 2 or so the text appears
set (ht, 'Clipping','on') ## The text disappears correctly
zlim ([0 3]) ## The text reappears correctly

Can I re-title this report to something like "Wrong text clipping limits"?

As for the fact that text objects are not taken into account when computing
axes limits, I guess that this behavior has been copied from Matlab's (don't
know if it is documented anywhere in ML doc).


Reply to this item at:


  Message sent via Savannah

reply via email to

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