Article View: comp.windows.x
Article #24004Re: graphicsexpose handling
From: Bob Toole
Date: Thu, 20 Jun 1991 16:12
Date: Thu, 20 Jun 1991 16:12
15 lines
1092 bytes
1092 bytes
> It goes click, gexpose, click, click, gexpose, gexpose - and the second > gexpose is handled *incorrectly*, ... Sorry about the post, my direct mail to you bounced. The solution to this at the Xlib level is after each XCopyPlane, wait until you get a GraphicsExpose or a NoExpose event. Better yet, don't do consecutive XCopyPlane calls unless you have had a GraphicsExpose event to repair damage or a NoExpose event to let you know there is no damage. This assumes the GC graphics-exposure flag is true. I am not sure what your toolkit is trying to do, but if you have source, you should be able to fix it. Somehow.
Technical Details
Message-ID:
<9106201612.AA14262@boa.MITRON.TEK.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!ora!bloom-beacon!dont-send-mail-to-path-linesReferences:
<25529@well.sf.ca.us>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!ora!bloom-beacon!dont-send-mail-to-path-lines From: bobt@boa.mitron.tek.COM (Bob Toole) Newsgroups: comp.windows.x Subject: Re: graphicsexpose handling Message-ID: <9106201612.AA14262@boa.MITRON.TEK.COM> Date: 20 Jun 91 16:12:34 GMT References: <25529@well.sf.ca.us> Sender: daemon@athena.mit.edu (Mr Background) Organization: The Internet Lines: 15