[net.micro.atari16] Slow response to the mouse left button

cw@vaxwaller.UUCP (Carl Weidling) (08/21/86)

	A couple of postings have mentioned programs that responded slowly
to the mouse's left button.  My version of Degas is notorious.  When I am
trying to quit, it ask's are you sure and has a little OK box.  I'll click
and click on that box before it responds.  Then, when it does responds and
puts up the regular menu, I may still be clicking furiously away and click
on some other command by mistake.
	Well, I remembered reading something about keyboard sequences
that correspond to mouse functions in the manual that came with my computer.
ALT INSERT correspond to clicking that button.  With some experimentation
I found that, after positioning over the OK box, if I hold those keys down
for a second, when I let up, the program responds.
	I just thought I'd pass this on for anybody who has any program with
this little glitch in it.
Regards,
Carl Weidling

-- 
Cleave yourself to logodaedaly and you cleave yourself from clarity.

lbl@druhi.UUCP (LocklearLB) (08/25/86)

In article <525@vaxwaller.UUCP>, cw@vaxwaller.UUCP writes:
> 
> 	A couple of postings have mentioned programs that responded slowly
> to the mouse's left button.  My version of Degas is notorious.  When I am
> trying to quit, it ask's are you sure and has a little OK box.  I'll click
> and click on that box before it responds.  Then, when it does responds and
> puts up the regular menu, I may still be clicking furiously away and click
> on some other command by mistake.
> 	Well, I remembered reading something about keyboard sequences
> that correspond to mouse functions in the manual that came with my computer.
> ALT INSERT correspond to clicking that button.  With some experimentation
> I found that, after positioning over the OK box, if I hold those keys down
> for a second, when I let up, the program responds.
> 	I just thought I'd pass this on for anybody who has any program with
> this little glitch in it.
> Regards,
> Carl Weidling
> 
> -- 
> Cleave yourself to logodaedaly and you cleave yourself from clarity.

An easier solution to the problem is to hold the mouse button down for a second.
That way you can avoid having to take your hand off the mouse, type, and then get
the mouse again.

Barry Locklear

ski@dciem.UUCP (Dave Eaton) (08/25/86)

In article <525@vaxwaller.UUCP> cw@vaxwaller.UUCP (Carl Weidling) writes:
>
>that correspond to mouse functions in the manual that came with my computer.
>ALT INSERT correspond to clicking that button.  With some experimentation
>I found that, after positioning over the OK box, if I hold those keys down
>for a second, when I let up, the program responds.


If you hold down the mouse button you will get the same results...


>	I just thought I'd pass this on for anybody who has any program with
>this little glitch in it.


Is it a glitch or is there a purpose for it?  Maybe someone at
Batteries Included can give us some insight...

Dave Eaton

D.C.I.E.M.
Toronto, Ontario
CANADA

apratt@atari.UUcp (Allan Pratt) (08/25/86)

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
\----------------------------------------------/