Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Why? (xany vs xmaprequest)
Message-ID: <8904261319.AA04845@expire.lcs.mit.edu>
Date: 26 Apr 89 13:19:20 GMT
References: <2544@mentor.cc.purdue.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 10


    event.xany.window != event.xmaprequest.window 
			       ^^^^^^^^^^^

When an event is received by the client, you want to be able to use
event.xany.window to correctly dispatch the event.  In the case of
the MapRequest event, the window that you want to use for dispatching
is in fact the "parent" field in the event, not the field named "window"
in that event.  I admit this is confusing, but I believe the events are
structured correctly.