octave-bug-tracker
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39529] graphics functions: unneeded new axis

From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #39529] graphics functions: unneeded new axis when parent is specified as prop/val
Date: Fri, 19 Jul 2013 22:12:57 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 
Follow-up Comment #2, bug #39529 (project octave):

Your code returns:

hf1 =
     1

hax1 =
  173.0011

hf2 =
     2

hax2 =
  347.0011

ans =
  347.0011

ans =
  347.0011

ans =
     2

ans =
  347.0011

ans =
     2

So octave just works as expected here. My interrogation is does octave really
have to change the currentaxes before processing the graphics objects in lower
level functions? Why not let it as is? AFAICS currentaxes is just the
(default) axes which is used if none has been specified.   

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/
reply via email to
[Prev in Thread] Current Thread [Next in Thread]