Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!mailrus!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: Dispatching Events To Spring-Loaded Widgets
Message-ID: <8810311729.AA01057@LYRE.MIT.EDU>
Date: 31 Oct 88 17:29:01 GMT
Article-I.D.: LYRE.8810311729.AA01057
References: <100920022@hpcvlx.HP.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 19

My reply to Fred's original posting to the Consortium mailing list:

To: Fred Taft <fred%hpcvxft@sde.hp.com>
Subject: Re: Dispatching events to spring loaded widgets 
In-Reply-To: Your message of Fri, 28 Oct 88 13:11:59 -0700.
             <8810282012.AA00318@hpcvxft.HP.COM> 
Organization: DEC/MIT Project Athena
Date: Fri, 28 Oct 88 17:52:37 EDT
From: Ralph R. Swick <swick@ATHENA.MIT.EDU>

The spec is not explicit on whether or not any of the routines that affect
the dispatching of events will have an impact on the _current_ event.

In the case you cite (registering a spring-loaded grab), it seems very
unlikely to me that the application would want the current event dispatched
to the new widget, and if it does then it should probably re-dispatch it
explicitly.

I suspect the modified behavior is therefore an oversight, but I invite
alternate opinions.