Path: utzoo!utgpu!attcan!uunet!lll-winken!csd4.milw.wisc.edu!dogie.macc.wisc.edu!uwvax!rutgers!att!pegasus!ech
From: ech@pegasus.ATT.COM (Edward C Horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Executing non-interrupt-level code after an interrupt
Message-ID: <2815@pegasus.ATT.COM>
Date: 21 Apr 89 18:30:57 GMT
References: <10050101@accuvax.nwu.edu>
Organization: AT&T ISL Middletown NJ USA
Lines: 19

> If a routine is called at interrupt time, what is the best way for it to get
> control back _not_ at interrupt time.  The only methods I recall hearing about
> are patching _GetNextEvent (and possibly _WaitNextEvent, but probably there
> is one patch which will cover all cases) and using jGNEfilter, which is a 
> low-memory global, and thus bad.  (Also, I don't know where it is documented.)
>						--David Maymudes

From article <10050101@accuvax.nwu.edu>, by bob@accuvax.nwu.edu (Bob Hablutzel):
>   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??)). 

Depending on what you're trying to accomplish, you can use the Deferred Task
Manager (IM V-465).  Deferred tasks get held until there are no interrupts
pending, just before return of control to the application.  Otherwise, there's
nothing for it but to set up a communications area in the DRVR's data area.
If you're an isolated Vertical-retrace task you may be SOL.

=Ned Horvath=