Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!versatc!mips!prls!philabs!ttidca!hollombe
From: hollombe@ttidca.TTI.COM (The Polymath)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Control-Break ignored in Turbo-C graphics mode....
Message-ID: <4212@ttidca.TTI.COM>
Date: 6 Apr 89 20:09:35 GMT
References: <89Apr4.202845edt.2759@godzilla.eecg.toronto.edu>
Reply-To: hollombe@ttidcb.tti.com (The Polymath)
Distribution: na
Organization: The Cat Factory
Lines: 18

In article <89Apr4.202845edt.2759@godzilla.eecg.toronto.edu> lansd@eecg.toronto.edu (Robert Lansdale) writes:
}	I have a small problem trying to get Control-Break to be
}recognized while in graphics mode, using Turbo-C's Hercules BGI driver
}(version 2.0). I initially revector the control-break handler to my own 
}handler using the ctrlbrk(handler) command, which works fine while in text
}mode, but is ignored once I switch over to graphics. I assume the
}BGI driver is vectoring the interrupt to itself. Any suggestions?

Does your graphics software spend much time in a tight loop?  I had a
similar problem with a mandelbrot program written in TC 2.0.  It would
ignore control-C interrupts until I put in some debug screen output.  Then
they worked just fine.

-- 
The Polymath (aka: Jerry Hollombe, hollombe@ttidca.tti.com)  Illegitimati Nil
Citicorp(+)TTI                                                 Carborundum
3100 Ocean Park Blvd.   (213) 452-9191, x2483
Santa Monica, CA  90405 {csun|philabs|psivax}!ttidca!hollombe