Message-Id: <m0yU9oM-000S3GC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>, djgpp AT delorie DOT com
Date: Tue, 28 Apr 1998 09:55:40 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Help, my brain hurts
In-reply-to: <XgTCiAAAXNR1EwUZ@talula.demon.co.uk>
Precedence: bulk

Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk> wrote:

> 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.

RHIDE use these functions but:

1) Or they are wrongly used (something is incomplete).
2) Or they doesn't work for the graphic modes used by Allegro.

I think Robert tested it in the same way I did: debugging TVision programs. In 
that case the routines work. For some reason they doesn't work with Allegro and 
I saw strange crashes when debugging Allegro and the mouse is on.
 
> 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 :-) 

:-))), I normally use it, the problem is when you need to debug something that 
depends on mouse clicks. In this case the user can disable the mouse before the 
zone to debug.
 
> 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 :-)

The second is ideal ... but, you know our fingers doesn't respond to our ideas 
;-)))
 
SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013