[Top][All Lists]

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

[Octave-bug-tracker] [bug #59123] Inherited axes properties incorrect/in

From: anonymous
Subject: [Octave-bug-tracker] [bug #59123] Inherited axes properties incorrect/inconsistent
Date: Thu, 17 Sep 2020 11:05:39 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0


                 Summary: Inherited axes properties incorrect/inconsistent
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Thu 17 Sep 2020 03:05:37 PM UTC
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: JZ
        Originator Email: jasmin.zimmer@batop.de
             Open/Closed: Open
                 Release: 5.1.0
         Discussion Lock: Any
        Operating System: Any



I attached two scripts where I can see some inconsistencies for which property
is inherited from a parent/related object and which isn't. 

In plotyyproblem.m, I have defined the position and the units property of the
axis, then call plotyy() for that axis. Now I know that technically, plotyy()
creates two new axes with new handles and everything, but I think I found a
bug concerning the inheritance of certain properties for the new axes. 

Under Linux, the output is 
Y1 units = normalized
Y2 units = normalized
and I can see both y-axes at the specified position, even though the units are
set to normalized again. 

Under Windows, the output is 
Y1 units = pixels
Y2 units = normalized
and the position property contains the specified position for both axes, so
that I can't see the secondary axes with the position being [50 50 300 300] in
normalized units. 
It looks like some properties aren't consistently inherited from the first
axis, but it's a little frustrating that it seems to depend on the OS of all

In colorbarproblem.m, a colorbar is added after the units and position of the
axis was modified. 
Here, under both Linux and Windows, the output is 
colorbar position = 320   50   18  300
colorbar units = normalized
and the colorbar is off-charts, just like the secondary y-axis under Windows
for the plotyyproblem.

I marked this as a bug for the 5.1 release but it also happens in 6.0.9. Also
I'm not sure if it's related to bug #58479 or any of the bugs linked there?


File Attachments:

Date: Thu 17 Sep 2020 03:05:37 PM UTC  Name: plotyyproblem.m  Size: 241B   By:

Date: Thu 17 Sep 2020 03:05:37 PM UTC  Name: colorbarproblem.m  Size: 224B  
By: None



Reply to this item at:


  Message sent via Savannah

reply via email to

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