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

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

[Octave-bug-tracker] [bug #52260] Axes appear upside down with Qt5


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #52260] Axes appear upside down with Qt5
Date: Mon, 23 Oct 2017 13:53:40 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Follow-up Comment #7, bug #52260 (project octave):

@Dan: Sorry for taking so long.
When I select the "Rotate" button and drag one of the upper subplots, the
corresponding lower axes rotate synchronously. They do not snap in place but
keep being drawn upside down. The same happens when I rotate the lower
subplots: The upside down axes drawn behind the corresponding upper subplot
rotate with the objects that are correctly drawn in the lower subplots.
I think that rules out option 3, does it?

I do not need to use subplots to get the upside down axes. A single axes
object in a figure also draws upside down (but obviously more in the "correct
place").

Could this be because I am running Ubuntu in a VM?
I see the following for "lshw -c video":

  *-display                 
       description: VGA compatible controller
       product: SVGA II Adapter
       vendor: VMware
       physical id: f
       bus info: address@hidden:00:0f.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=vmwgfx latency=64
       resources: irq:16 ioport:1070(size=16) memory:e8000000-efffffff
memory:fe000000-fe7fffff memory:c0000-dffff


I also tried to find differences between "draw_axes_boxes" and
"draw_axes_planes" because the planes are appearing in the correct orientation
and the boxes are not. Swapping the order in which they are drawn doesn't make
a difference.
I also tried drawing one line at the edge of one of the planes in
"draw_axes_planes" by adding the following lines at the end of that function:

    double black[3] = {0, 0, 0};
    glColor3dv (black);
    set_linestyle ("-");
    glBegin (GL_LINES);
    glVertex3d (xPlaneN, yPlaneN, zPlane);
    glVertex3d (xPlane, yPlaneN, zPlane);
    glEnd ();


That line appeared in the correct place. So something might be going wrong on
my system when assigning ypTickN or zpTick. Will investigate further.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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