[racket] XNextEvent blocking 'read' in other thread?

From: Laurent (laurent.orseau at gmail.com)
Date: Wed Nov 7 14:44:55 EST 2012

Also, both versions seem to suffer a heavy cost of a few seconds of
> initialization compared to the basic XNextEvent version.

Hmm, no, that seems to be due to some other problem: to force
synchronization, I need to generate several events at first for the handler
to catch up. There might be some XFlush or XSync or something missing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20121107/3b2e3a50/attachment.html>

Posted on the users mailing list.