Pierre Phaneuf said:
What is cool about this is that in a regular program, you can call
XCopyArea right before doing the “real work” of the program, then call
XSync right before sending another XCopyArea (to make sure the first one
is completed, if it already is finished, the XSync will return
immediately).
HEY! That’s a cool trick to know! If I ever get into using raw Xlib
again, I’ll have to remember that. 
-bill!
William Kendrick wrote:
What is cool about this is that in a regular program, you can call
XCopyArea right before doing the “real work” of the program, then call
XSync right before sending another XCopyArea (to make sure the first one
is completed, if it already is finished, the XSync will return
immediately).HEY! That’s a cool trick to know! If I ever get into using raw Xlib
again, I’ll have to remember that.
Since the X server in X11 forces you to suffer context switching because
it is in another process (which sucks, hence direct rendering), you
might as well make use of it!
Note that this will make your game take advantage of a dual processor
system without using multiple threads or processes! (the X server should
do the blitting on one CPU while you do other stuff on the other CPU)–
Pierre Phaneuf
Ludus Design, http://ludusdesign.com/
“First they ignore you. Then they laugh at you.
Then they fight you. Then you win.” – Gandhi
unsubscribe