Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!cwjcc!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R Swick)
Newsgroups: comp.windows.x
Subject: Re: Events, children, and window manage
Message-ID: <8902221334.AA26737@LYRE.MIT.EDU>
Date: 22 Feb 89 13:34:07 GMT
References: <60200006@mcdurb>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 22


     Date:  21 Feb 89 17:37:00 GMT
     From:  mcdurb!ebina@uxc.cso.uiuc.edu

     
     and as a child of that widget I have another composite widget that uses
     XtAddEventHandler to catch Button1Motion events.

     The parent widget receives its events properly, but the child widget never
     gets its events.  If I then kill the window manager (I am using uwm),
     the child widget will start getting its events correctly.

If you are using the default button bindings in uwm, the button press
event is propagating up the window tree to the root window where it
is then going to uwm, causing the motion events to also go to uwm.

The child needs to select for ButtonPress (translation <Button1Press>
if you are using translation tables) if it wants to be sure to get
the MotionNotify events.  The event can be discarded if you're not
actually interested in it.

This is a common trap; I've fallen into it many times myself.