Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!steinmetz!mizar!jesup
From: jesup@mizar.steinmetz (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: 1.2 Bugs
Message-ID: <7324@steinmetz.steinmetz.UUCP>
Date: Sat, 12-Sep-87 01:51:43 EDT
Article-I.D.: steinmet.7324
Posted: Sat Sep 12 01:51:43 1987
Date-Received: Sun, 13-Sep-87 01:55:20 EDT
References: <15776@aspvax.UUCP>
Sender: root@steinmetz.steinmetz.UUCP
Reply-To: jesup@mizar.steinmetz.UUCP (Randell Jesup)
Organization: General Electric CRD, Schenectady, NY
Lines: 26

In article <15776@aspvax.UUCP> eraps2@aspvax.UUCP writes:
>Also interesting is the way the system keeps track of key-downs.  I was
>playing with Disable()s and came across an interesting effect -> If I
>pressed down a key before a Disable(), and then released it before the
>corresponding Enable() [yes, I did expect to lose KB data], the system
>held own that key FOREVER, yes, even though it was receiving key-up's
>(by pressing the key again), it left the key ON.  My best guess is that
>someone is counting the number of keyups vs keydowns (note that I could
>clear the condition by running the experiment in reverse -> run, press
>key, after Enable(), release).  Since there is no need to count
>keyups/downs, I figure that something else in the chain is keeping
>track.  Perhaps the WindowToFront() code locks out ints for a bit?

>Rob Ginn     ...!burdvax!jtids!aspvax!eraps2

This sounds similar to a problem I've had from time to time, where the
arrow keys move the mouse as if the left-A key was pressed.  Pressing and
releasing it doesn't help, but I have been able to fix it sometimes by
rapidly playing with the key while moving the mouse from window to window
clicking the left button.  More often, I have to reboot or live with it.

As far as I can tell, it happens during a boot, not after doing a bunch
of stuff.
	Randell Jesup  (Please use one of these paths for mail)
	jesup@steinmetz.UUCP (uunet!steinmetz!jesup)
	jesup@ge-crd.ARPA