Update of bug #17717 (project gnustep):
Assigned to: None => CaS
_______________________________________________________
Follow-up Comment #34:
I haven't been able to work out as much as I hoped from the trace of
GWorkspace events ... One section looked quite interesting, but after going
through it carefully I concluded that it was doing just what we might expect
when the finder window was resized. I guess we need to figure out more
detailed debug about what is happening in the gui and buffering in response
to the events.
I'm wondering if this might all be some problem with the shared memory image
buffering getting out of sync somehow.
Q. Does the GWorkspace issue persist if you set XWindowBufferUseXShm 0?
Can you reproduce it with the xlib backend?
Unless the answers to the above are NO, coordinate mapping generally is still
the prime suspect, and I think that adding a lot of debug to any chages to
size and offset information should help us.
_______________________________________________________
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
