[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50680] Strange behaviour of colororder proper
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #50680] Strange behaviour of colororder property |
Date: |
Thu, 30 Mar 2017 11:20:18 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Update of bug #50680 (project octave):
Release: 4.0.3 => dev
_______________________________________________________
Follow-up Comment #1:
Hi,
This is all expected and compatible with ML (but probably insufficiently
documented):
* Example 1: "hold on" creates an axes which will be used for further high
level plotting since it has its "nexplot" property set to "add" by "hold"
function (see "help newplot")
* Example 2: after "hold on" has created a first axes, you create a second one
with "axes". The second one has "nexplot"->"replace" (the default) and will
thus be reset by "newplot"
* Example 3: you create a second axes that covers the first one, use "set
(gca, 'colororder', jet);" instead of "axes (...)"
There is already a request to better document this behavior but I can't find
it right now.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50680>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/