Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!hplabs!hp-pcd!hpcvlx!fred
From: fred@hpcvlx.HP.COM (Fred Taft)
Newsgroups: comp.windows.x
Subject: Dispatching Events To Spring-Loaded Widgets
Message-ID: <100920022@hpcvlx.HP.COM>
Date: 28 Oct 88 21:57:44 GMT
Article-I.D.: hpcvlx.100920022
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 19


Between the R2 and R3 intrinsics I have noticed a different behavior 
in the way button and key events are being dispatched to a spring 
loaded widget.

Under the R2 toolkit, if a button event was received, and the grab list
was empty, the event was ONLY dispatched to the widget the event occurred
in; if this widget, as a result of processing the event, added an exclusive,
spring loaded widget to the grab list, the event was not then dispatched to
the new spring loaded widget.

Under the R3 toolkit, this behavior has changed.  Now, after dispatching to
the original widget, the toolkit also looks to see if there are any exclusive
spring loaded widgets, and dispatches to them.  Since the original widget
added an exclusive spring loaded widget to the grab list, it also gets the
opportunity to process the event.

Was this new behavior intended, or did it sneak in accidentally?  It not
only has the potential of breaking certain types of widgets, but it also
can break applications!