[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45356] Wrong tick labels when limits are set
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #45356] Wrong tick labels when limits are set manually |
Date: |
Fri, 19 Jun 2015 12:41:02 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 |
URL:
<http://savannah.gnu.org/bugs/?45356>
Summary: Wrong tick labels when limits are set manually
Project: GNU Octave
Submitted by: pantxo
Submitted on: ven. 19 juin 2015 12:40:55 GMT
Category: Plotting
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.0.0
Operating System: Any
_______________________________________________________
Details:
Octave returns wrong tick labels when limits are set manually:
plot (1:10)
xlim ([.5 10.5])
get (gca, 'xtick')
get (gca, 'xticklabel')
The displayed xlabels are correct, i.e [2 4 6 8 10], while the returned values
for "xtick" and "xticklabel" properties are consistently wrong: [0 2 4 6 8 10
12]. These are the labels we would have obtained if xdata had actually
extended from 0.5 to 10.5 and the xlimmode had been "auto".
I could check in ML 3013a that displayed and returned values are consistent,
i.e. [1 2 3 4 5 6 7 8 9 10].
I *wouldn't* expect that Octave follows ML exactly (i.e. increments of 1
instead of 2), but I do expect displayed and returned values to be consistent
as in ML.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45356>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #45356] Wrong tick labels when limits are set manually,
Pantxo Diribarne <=