Path: utzoo!attcan!utgpu!barry
From: barry@gpu.utcs.utoronto.ca (Barry Lay)
Newsgroups: comp.sys.atari.st
Subject: Re: The 'PHANTOM TYPIST'
Message-ID: <1990Feb16.153809.19595@gpu.utcs.utoronto.ca>
Date: 16 Feb 90 15:38:09 GMT
References: <900204.10484196.021631@SFA.CP6> <1990Feb13.114858.5081@bath.ac.uk> <8D0_&*@masalla.fulcrum.bt.co.uk>
Organization: UTCS Public Access
Lines: 17

The issue of having to move the mouse slightly when selecting menu items 
reminds me of a similar problem on my machine.  I have had instances when
a double click on a program doesn't do anything until the mouse moves.  It
was suggested to me that the button up packet from the Ikbd was being lost
somehow, and the GEM didn't realise that the button was indeed up until the
next packet, which was a mouse move, had the button flag cleared.  I get this
happening in the desktop as well as in programs.

Having played around with writing a program which waits for all sorts of
things, I have discovered that it is not difficult at all to loose input.
You also have to be very careful about how the keyboard interrupts are
handled so that you don't overrun the internal queues when someone types
quickly.  Part of the solution is realising that you are single threading
all of those inputs through evnt_multi() in a loop.  Plenty of opportunity
for deadly embrace or message explosion resulting in a crash.

Barry