arm@moriah.UUCP.UUCP (04/03/87)
The following happens in version 10. Two or more different processes call XSelectInput to show that they want to receive the same event. There aren't any pending events of this type so each process blocks when they call XNextEvent. When the event is finally available one of the processes receives it. The other(s) continues to block. Since each process is unaware that any other process wants the event it doesn't know when to call XPeekEvent instead of XNextEvent. Will version 11 allow more than one process to get the same event? Alan Michels Silvar Lisco Menlo Park, CA sun!silvlis!arm
jg@jumbo.UUCP (04/03/87)
In article <8704030042.AA01831@moriah.silvlis.com> arm@moriah.UUCP (Alan Michels) writes: > >Will version 11 allow more than one process to get the same event? > The short answer is yes, but there are a few event types that interact with grab sematics that only a single client can select on at one time. In particular, if both down and up keyboard events are requested, only a single client can select for the keyboard events. For details, look at the protocol document. - Jim
RWS@ZERMATT.LCS.MIT.EDU.UUCP (04/03/87)
Date: 3 Apr 87 05:41:14 GMT
From: jumbo!jg@decwrl.dec.com (Jim Gettys)
In
particular, if both down and up keyboard events are requested, only a
single client can select for the keyboard events. For details, look
at the protocol document.
Please do look, since Jim's statement is incorrect. The only restricted
event types are SubstructureRedirect, ResizeRedirect, and ButtonPress.