From: ovek AT arcticnet DOT no (Ove Kaaven)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug Report on RHIDE
Date: Mon, 09 Mar 1998 14:18:31 GMT
Organization: Arctic Net AS
Lines: 21
Message-ID: <3503f8bd.948951296@isflak.arcticnet.no>
References: <Pine DOT D-G DOT 3 DOT 93 DOT 980309081126 DOT 5105A-100000 AT pessoa DOT ci DOT uminho DOT pt>
NNTP-Posting-Host: village-dos.arcticnet.no
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Alberto Manuel Brandao Simoes <mc23801 AT ci DOT uminho DOT pt> wrote:
>	I am programming a game using  Allegro 3.0 and I have created a project for it.
>	Some times I run the program, modify the the main file a bit, and run it again by pressing
>Ctrl-F9. Instead of re-making the executable file, rhide simply runs it. Then, I exit the
>game, and press F9 (Make), but rhide tells me the excutable is up to date.

Remember to save the main file (F2) first. Or check your system clock.
I also hear FAT32 may have some problems.

>	At this point something weird happens: my keyboard behaves as if I had the Control key
>pressed all the time. I have to quit rhide and re-enter it to fix this problem.
>	I am not sure if this is a problem with rhide, since I install a keyboard interrupt
>handler with a call to Allegro's install_keyboard(); .

I usually had this problem too. When you hit Ctrl-F9 to start the
program, and release the Ctrl only *after* install_keyboard() is
called, the BIOS never gets to know that you did release it, so when
you return it still thinks you do. It's easy to fix when it happens,
just hit Ctrl again after the program exits, or just release the Ctrl
faster when you run it.