[Octave-bug-tracker] [bug #50511] colororder property seems to be reset on plot

[Andrei Kramer]

Follow-up Comment #4, bug #50511 (project octave):

Well, I tried to change the order (before I posted this bug).
Plotting first, then changing the colororder property has no effect on the
plot. Issuing a command like ylim(), that could potentially cause the plot to
update, doesn't help with the colors.

But, setting the colororder after plot() will make my little if statement go
to printing the "colororder worked." line.

The plot does not change however.

Update: I also tried it with octave 4.2.0 on Gentoo Linux, same problem in
both cases. So, it doesn't seem to be my specific build.

So, in summary:
plot() then set(gca,'colororder',CO); does not change the plot.

@rik5: doesn't your test-code show that my proposed order is correct?
I see

set (hax, 'colororder', [1 0 0; 0 1 0; 0 0 1])
[...]
plot (1:10)

So, this property is supposed to be set before plotting. 

And, besides, I think that it should work either way, ideally. But, I'd be
content if one of the orders worked.

    _______________________________________________________

Reply to this item at:

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

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