Follow-up Comment #31, bug #17717 (project gnustep):
I think the size of XWindowBuffer is never updated even with the latest
backend.
Here is a short track:
1. 2006-09-24 12:42:07.330 Ink[2963] rect {x = 1; y = 6; width = 390; height
= 426}, rectangle (0, 0, 390, 426)
A new Expose event goes into XGServerEvent (the new patch).
rect = [self _XWindowRectToOSWinRect:...];
Both the rect and rectangle has the right size, 390x426.
2. 2006-09-24 12:42:07.377 Ink[2963] -_exposeRect: (sx, sy) = (384, 426),
rect = {x = 0; y = 0; width = 390; height = 426}
2006-09-24 12:42:07.378 Ink[2963] sx 384, sy 426, x 0, y 0, w 390, h 426
-exposeRect: in XWindowBuffer is called with NSRect (390x426).
But the sx, sy are still 384x426, which is the size when it is created in
-windowBufferForWindow:depthInfo:
3. 2006-09-24 12:42:07.383 Ink[2963] X-Windows error - BadValue (integer
parameter out of range for operation)
on display: :0.0
type: 0
serial number: 2365
request code: 143
Error occurs when XShmPutImage() is called.
I don't see the +windowBufferForWindow:depthInfo: is called
when new expose event occurs. Maybe that's the bug.
PS. Now, it works with XWindowBufferUseXShm 0.
PPS. It is not associated with left-mouse down.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?17717>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
