Mail Archives: djgpp/1999/08/01/22:15:25
I don't use RHIDE or Allegro, but I'm willing to hazard a guess as to
what is happening (I've seen it with other IDEs). You have to hold
control (and maybe press something else) to run the program, by any
chance?
In that case:
-You press control, BIOS handler detects it and flags it
-You press the other key, BIOS detects it and passes it to Allegro (as
a control key, because control is being held)
-Your program runs, takes over the keyboard handler
-You release both keys, the Allegro handler is notified (but not the
BIOS handler)
-Your program finishes, points handler back at BIOS routine
-At this point, BIOS still thinks control is being held (ie, it is
still flagged as 'depressed') because its handler never got a "key
up".
The quick fix is to simply press and release control after your
program has finished. Or, you could wait until control is no longer
depressed in your program before installing the Allegro keyboard
handler.
Davin.
On Sun, 1 Aug 1999 21:10:58 -0400, Edward J Sanville
<edwards AT alberti DOT unh DOT edu> wrote:
>I have RHIDE version 1.4, and Allegro version 3.11.
>
>Whenever I try to compile one of my programs, (or even Shawn
>Hargreaves's), that uses the Allegro keyboard handler, it completely
>screws up the keyboard when I return to the RHIDE. It acts like I'm
>constantly holding down the control key. Anyone lese have this bizzare
>problem?? I think it may have started in Allegro version 3.1, and I'm
>surprised no one else has detected this weird bug.
>
>
__________________________________________________________
*** davmac - sharkin'!! davmac AT iname DOT com ***
my programming page: http://yoyo.cc.monash.edu.au/~davmac/
- Raw text -