Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!arc.UUCP!alan
From: alan@arc.UUCP (Alan Mimms)
Newsgroups: comp.windows.x
Subject: Why XSendEvent sets hibit of type?
Message-ID: <8801090141.AA08906@arc.com>
Date: 9 Jan 88 01:41:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 25

Why the devil isn't the strange behavior of events queued by
XSendEvent (rather than the usual way) more loudly proclaimed in the
manuals?  XSendEvent sets the high-order bit in the event type code!
This is bad since there is no way to disable this "feature" should one
wish to use one client to cause events in another client.

I suppose it is reasonable to provide a way to discern events directly
from the server and events that were artifically generated, but
couldn't it be either (a) optional (good) or (b) invisible unless you
explicitly look for it (better)?

I wonder if maybe it would be prudent to make this "feature" optional?
Is there such a hook?  We're presently getting around this by hacking
clients to mask the event type with 0x7F before they use the value or
by making a call to XESetWireToEvent to register a routine which makes
a teeny change in the event after it's converted.

Any thoughts?  Can we hear some pro/con discussion?  (Or better yet,
will it "be fixed in the next release"?)

Alan Mimms		...!sun!texsun!arc!alan
ADVANSOFT Research Corp.
4301 Great America Pkwy
Santa Clara, CA   95054
(408) 727-3357