octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39483] axes "handlevisibility" not properly h


From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #39483] axes "handlevisibility" not properly handled with new children objects
Date: Wed, 17 Jul 2013 21:39:33 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0

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

Yes I did test the first example in ML and it returns empty matrix. The
problem has finally nothing to fo with "handlevisibility", but with the
presence of a current axes. The following example also returns empty matrix
for the current axes in ML:


close all
figure (1);
ax = axes ('parent', 1);
figure (2);
line ('parent', ax)
cf = get (0, 'currentfigure');
ca = get (cf, 'currentaxes');
disp (sprintf ('current figure: %d, current axes %fn', cf, ca))


returns "current figure: 2, current axes  " (thus empty matrix), and "ax" has
been populated with a new line with no axes creation in figure (2).

In octave a new axes is created in figure (2) before populating "ax" with the
line, result : "current figure: 2, current axes -32.447683". An example patch
for line.m is attached (which depends on the previous one).

(file #28607)
    _______________________________________________________

Additional Item Attachment:

File name: line_avoid_gca.patch           Size:0 KB


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]