[Octave-bug-tracker] [bug #50680] Strange behaviour of colororder property

[Francesco Potortì]

URL:
  <http://savannah.gnu.org/bugs/?50680>

                 Summary: Strange behaviour of colororder property
                 Project: GNU Octave
            Submitted by: pot
            Submitted on: Thu 30 Mar 2017 03:47:21 PM CEST
                Category: Plotting with OpenGL
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Documentation
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.3
        Operating System: GNU/Linux

    _______________________________________________________

Details:

This bug follows up on bug #50511.

In the answer to that bug, I discover that this code works:


> close; figure; hold on; set(gca,'colororder',jet);
> a=1:20; plot(a,a+a')


The first problem is that this is counterintuitive. I suggest that this code
be added in the docs as an example, maybe following the text of the
'colororder' line property.

The second problem is that this code does not work:


> close; figure; hold on; axes('colororder',jet);
> a=1:20; plot(a,a+a')


Apparently, axes does nothing with the colororder property, yet does not give
an error. This may be an axes bug or a documentation bug, I do not know.

Third, in the following instance axes() corrupts the plot in a strange way:


> close; a=1:20; plot(a,a+a');
> axes('colororder', jet);


the lines disappear after running axes(), and moreover the axis labels are
corrupted.

All the above code is run under Octave 4.0.3 on Debian.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50680>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/