Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!tut!santra!mcsun!hp4nl!fwi.uva.nl!kim!freek
From: freek@fwi.uva.nl (Freek Wiedijk)
Newsgroups: comp.sys.mac.programmer
Subject: Re: best way to detect command-. interrupt?
Message-ID: <352@fwi.uva.nl>
Date: 29 Dec 89 00:45:22 GMT
References: <694@nems.dt.navy.mil> <33392@ucbvax.BERKELEY.EDU> <9421@hoptoad.uucp>
Sender: news@fwi.uva.nl
Reply-To: freek@fwi.uva.nl (Freek Wiedijk)
Organization: Faculteit Wiskunde & Informatica, Universiteit van Amsterdam
Lines: 16

In article <9421@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
 >I'm not really sure that there is any good way, short of patching the
 >keyboard driver -- and even that would be an application-specific
 >patch, so if you *are* giving other applications time, it could fail to
 >be invoked when the actual keypress happens.  I suppose you could insert
 >a front-end to the driver into the unit table, but that seems like a
 >big mess for such a small operation.

Isn't it possible to patch PostEvent, to make it set a flag somewhere,
and have your "calculation" test this flag often?

Someone told me that this is what Mathematica does.

--
Freek "the Pistol Major" Wiedijk                  Path: uunet!fwi.uva.nl!freek
#P:+/ = #+/P?*+/ = i<<*+/P?*+/ = +/i<<**P?*+/ = +/(i<<*P?)*+/ = +/+/(i<<*P?)**