Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!oliveb!apple!darin
From: darin@Apple.COM (Darin Adler)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Executing non-interrupt-level code after an interrupt
Message-ID: <1475@internal.Apple.COM>
Date: 20 Apr 89 08:46:38 GMT
References: <1631@husc6.harvard.edu> <10050101@accuvax.nwu.edu>
Organization: Apple
Lines: 14

In article <10050101@accuvax.nwu.edu> bob@accuvax.nwu.edu (Bob Hablutzel) writes:
>   If the interrupt handler is part of an application, then you could always
> post an application defined event (Using PostEvent, on the page between
> IM-67 and IM-69 (can you tell what key on my keyboard doesn't work??)). 

This is a bad idea. Under MultiFinder (and possibly other future environments),
a posted event goes the the frontmost application (at the time the event is
posted). In many instances, this will not be the application that the interrupt
handler is part of. For this reason, we discourage the use of application-
defined events under MultiFinder.
-- 
Darin Adler, System Software Scapegoat, Apple Computer
	Internet: darin@Apple.com
	UUCP: {nsc,sun}!apple!darin