🚀 go-pugleaf

There has been some talk lately about slow responses to the mouse buttons.
I would like to clear some of that up.

When you press a mouse button, GEM starts a delay timer.  It waits for that
timer to expire before returning the mouse event to the application.  During
that time, GEM is checking for things like double-clicks and chords
(multiple mouse buttons down simultaneously).  At the end of the delay, it
compiles an idea of what the user did, and returns from the wait if the
waited-for condition happened.

The user can set this delay time from the Control Panel: that's what the
"sleeping/running" mouse icons mean.  The higher the number, the shorter the
delay time.

To demonstrate this, open your Control Panel and click on the 0 box. Now go
down to the keyclick box and click on it a couple of times.  Notice the
delay between your click and the change in the box.  Go back and select 4
instead of 0, and click on the keyclick box again.  The delay was shorter
this time, wasn't it?  The delay is the amount of time you have to
double-click before GEM gives up and registers a single-click.

Now about Degas:  I believe the author of Degas wrote his own dialog
handler.  In any case, the apparent delay time between button-down and
action is a LONG time.  Multiple-clicks won't help.  The way out of a Degas
dialog is to HOLD THE BUTTON DOWN over Ok/Cancel/whatever.

/----------------------------------------------\
| Opinions expressed above do not necessarily  |  -- Allan Pratt, Atari Corp.
| reflect those of Atari Corp. or anyone else. |     ...lll-lcc!atari!apratt
\----------------------------------------------/