[Xquartz-dev] border drawing problem in xorg-server-1.7.3

[Martin Otte]

Jeremy,

I'm going to describe the last  remaining problem the I see with border drawing in the recent 1.7.3 server, using the simple border.c example code that I sent a few months ago. I'll attach the simple code again so that you can easily have the code.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: border.c
Type: application/octet-stream
Size: 1370 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20091203/244d23ce/attachment-0001.obj>
-------------- next part --------------


When I compile and run the code, it just creates a window with an internal window that has a border. Previously, the internal border was not shown, but you have fixed this in the recent servers. I have attached initial.png that shows the initial correct appearance when I first run the program:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: initial.png
Type: image/png
Size: 20273 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20091203/244d23ce/attachment-0003.png>
-------------- next part --------------


now when I drag the handle to make the window smaller to obscure the border (minimized.png):

-------------- next part --------------
A non-text attachment was scrubbed...
Name: minimized.png
Type: image/png
Size: 19838 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20091203/244d23ce/attachment-0004.png>
-------------- next part --------------

 
and then drag the handle to make the window larger again, exposing the internal border again, the internal border becomes corrupted (reexposed.png):

-------------- next part --------------
A non-text attachment was scrubbed...
Name: reexposed.png
Type: image/png
Size: 23369 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20091203/244d23ce/attachment-0005.png>
-------------- next part --------------


The only instance I can find when the internal border is always shown correctly is when the window is all the way in the upper-left corner of my display. The further the window is from the upper-left corner, the more corruption there is of the internal border.

With a larger program that I have which displays many buttons of various sizes, even the initial appearance of the borders can be slightly corrupted if the window is away from the upper-left corner.

In case this is system/graphic card dependent, I'm running this on a MacBook Pro. Can you verify the same behavior with my simple test case?

Thanks,
Martin