Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!cernvax!jones
From: jones@cernvax.UUCP (robert jones)
Newsgroups: comp.windows.x
Subject: XSendEvent problems
Keywords: XSendEvent XLib
Message-ID: <1048@cernvax.UUCP>
Date: 14 Aug 89 09:00:35 GMT
Reply-To: jones@cernvax.UUCP (robert jones)
Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland
Lines: 32
References:

Environment: VAXstation 3200 b/w. VMS 5.2-42E. MIT C Bindings for XLib.

I am having a strange effect when using XSelectAsyncInput in my XLib program.
Most events are delivered to my AST routine normally, except client messages
which seem to be buffered. I have set XSynchronise but this has no effect.
The pending client messages are delivered after some other type of event is
delivered.

As a test, I set up the following scenario:
process 1: creates a window and sends client events to the window in response
	   to user input

process 2: calls XSelectAsyncInput, XSelectInput for process #1's window then
	   calls sys$hiber and waits for the AST to be called.

process 3: calls XSelectInput for process #1's window then loops on
	   XNextEvent

All processes set XSynchronize.

process 3 receives the client messages as they are sent by process 1, but
process 2 does not receive them until some other event happens (eg I stop
process 1 thereby deleting the window).

Has anyone else met this behaviour?
Thanks for listening.

Bob Jones

jones@online.decnet.cern.ch (EAN)
vxcern::jones (hepnet)
jones%online@cernvax (bitnet)