[Octave-bug-tracker] [bug #39767] initial axes are not ordered properly

[Rik]

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

I'm in violent agreement with you.  kids(1) should be the last axes created
and it *is* the last axes created according to


set (kids(1), 'color', 'g');


The %!test you wrote shows that the position value for axes 1 is being
assigned to axes 2 and vice versa, but it doesn't seem to show an incorrect
ordering of axes.



    _______________________________________________________

Reply to this item at:

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

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