Mail Archives: djgpp/1998/04/27/18:33:49
James W Sager Iii writes:
>I am using rhide+allergo and I'm using mouse routines.
>When I step through my code and then try to reset it or
>even exit rhide I get a bunch of cryptic errors and the
>program may or may not lock up, and if it doesn't lock
>up, it shells to dos.
>
>Someone mentioned that this problem is because I'm using the
>mouse.
That sounds very likely to me. I'm not that familiar with Rhide, but I
would be very surprised if it can reliably save and restore the mouse
driver state. DOS does provide some functions for doing this, but they
aren't implemented on every mouse driver, and even if your system
supports them, I don't know whether Rhide will actually use them.
My advice is to disable the mouse while you are debugging your program
(if it requires a mouse, well, it is about time you got around to adding
some keyboard shortcuts :-)
Debugging Allegro programs is something of a black art. It is great when
it works, but you will often have problems when the debugger can't
correctly restore all the hardware state. For this reason, I rarely use
debuggers myself, preferring to rely on printf traces and/or just
writing things correctly in the first place :-)
>Is there some way I can bind quick keys to rhide such that when I hit
>a certain button that I can run an external program: IE a program
>with the line: allegro exit();
That wouldn't help. Running an external program that calls
allegro_exit() is meaningless: you need to reset the program that is
being debugged, not some other child program that also happens to be
using bits of Allegro...
--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
"Pigs use it for a tambourine" - Frank Zappa
- Raw text -