Comment 4 for bug 1485199

Edward Hennessy schreef op zo 16-08-2015 om 00:53 [+0000]:
> I'm also unable to reproduce in Linux Mint 17.2, KDE, and VMWare
> graphics.
>
> What is your screen resolution? I'll try changing to that and re-test.

I have a dual-screen setup, with one screen 1680 x 1050, and the other
1280 x 1024.

> Also, can you try the following:
>
> 1. Start gschem
> 2. Alter the zoom (in or out)
> 3. Maximize the main window
>
> It is your procedure to replicate the issue, but with a zoom in the
> middle. I'm thinking it could be a set of parameters sent to the zoom
> code that could be contributing.

Step 2 can be anything, except enlarging (and that includes maximizing)
the main window.
However, I found another way to trigger the bug, yielding a little more
information:

1. Start gschem
2. Enlarge the main window by dragging one of the borders in an outward
direction.

After a few pixels, the border stops moving, the mouse cursor detaches
from the border, and gschem freezes. From a cold start of gschem, this
happens when the main window reaches a width of 1278 pixels or a height
of 985 pixels, although I don't believe that these dimensions have any
particular significance (see below). Attached you find an example of a
gschem window with this width, showing a blank area where an overlapping
window was closed and gschem failed to redraw.

I also notice that this happens only when BOTH the bottom and right
tabbed windows are visible. Even when the main window is much smaller,
the bug is triggered as soon as I start dragging the borders.

As said, I can make gschem snap out of it by scrolling the mouse wheel
in the main viewport, and then drag the right window into invisibility
-- and I find this also works with the bottom window. Then I can restore
both edge widows and work without problems -- until I resize the main
window again, that is.

If there's any way that I can start gschem in some sort of debug or
trace mode to obtain more information, please let me know.

Best regards,

Richard Rasker