Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!rutgers!gatech!emory!stiatl!meo
From: meo@stiatl.UUCP (Miles O'Neal)
Newsgroups: comp.windows.x
Subject: Re: (none)
Message-ID: <6924@stiatl.UUCP>
Date: 18 Sep 89 19:11:15 GMT
Organization: Sales Technologies Inc., "Where noone has even reached the Bridge yet."
Lines: 23

In article <8909161835.AA13023@aristotle.Jpl.Nasa.Gov> pjs@ARISTOTLE-GW.JPL.NASA.GOV (Peter Scott) writes:
|On a number of quite different windowing systems I've observed
|the behavior of a widget such as a command button, which highlights
|when it's pressed, perform the highlighting but not the callback
|that's also associated with it.  In other words, the button flashes,
|but the action that's supposed to happen doesn't.  This generally
|happens when the button is pressed quite quickly after a sequence of
|other actions has been taken.

I haven't seen this in X11. What often happens is that the callback is
tied to the Button*Up* event, and the user presses a button near the edge
of the widget, accidentally (or intentionally) moves out of the widget,
and releases the button. By the time the ButtonUp event is triggered,
the mouse is already out of the widget, and the widget is in the process of
unhighlighting itself anyway.

The only other possibility I can think of is that if, again, there is mouse
motion associated closely in time with the button release, the events might
arrive out of order. I don't know offhand whether that would cause this
problem or not.

-Miles
gatech!stiatl!meo