Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: EventMask for XSendEvent
Message-ID: <9005091236.AA02016@expire.lcs.mit.edu>
Date: 9 May 90 12:36:30 GMT
References: <26900116@m.cs.uiuc.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 31

Please remember that detailed context is usually important ...

    In R3, the following sends off the Client Message:
	XSendEvent(xr->dpy,xr->id,False,(unsigned long)~0L,&ev); 
    Under R4, neither that nor
	XSendEvent(xr->dpy,xr->id,False,(unsigned long)-1L,&ev); 

Without knowing the structure of the receiver (what the window hierarchy
is and what clients are selecting for what events), it's really hard to
know what the problem is.  I note in passing that the R4 Xt uses the
first form of XSendEvent noted above for selections, and it works fine.

	XSendEvent(xr->dpy,xr->id,False,
		SubstructureNotifyMask | SubstructureRedirectMask,
		,&ev); 
    That works, but only for messages to the window manager, not for a
    general Client Message receiver (which does not have either of those events
    selected).

Sounds like you are sending to the wrong window, sending to the window manager's
frame rather than the true client window.  Perhaps part of your confusion is
that you moved from uwm in R3 to twm (or some other reparenting WM) in R4.
Given a top-level window, try using XmuClientWindow to find the real window to
send to.

    What I want to know is why I can't send it with _all_ the event
    mask bits set? Was something changed here from R3 to R4?

Yes, the server was made to obey the protocol here.  You can't use all ones
because that includes some illegal bits, which should result in the server
generating a protocol error.