Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac
Subject: Re: article about jGNEFilter in MacTuto
Message-ID: <2703@hoptoad.uucp>
Date: Tue, 11-Aug-87 08:34:09 EDT
Article-I.D.: hoptoad.2703
Posted: Tue Aug 11 08:34:09 1987
Date-Received: Thu, 13-Aug-87 01:36:55 EDT
References: <164500042@uiucdcsb>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Centram Systems, Berkeley
Lines: 20

All such filters are not long for this world and should be avoided.  I
believe that you never need to patch GetNextEvent or intercept it in any
case, since you can always do whatever extra processing is needed normally
inside your main event loop, and it is nearly trivial to install a filter
procedure in all your modal dialogs which will handle events as neccessary.
In TOPS Terminal, I have done just this, with the result that all background
type actions, such as receiving data on a terminal connection, take place
behind any modal dialogs that come up.  Don't ever patch a trap unless you
absolutely have to!  And *never* use a low-memory-global-based hook, because
it will stop working very soon if it hasn't already.

In fact (it should be kosher to say this now that MultiFinder is all over
the trades and being announced in Boston), all low-memory globals are going
away pretty soon.  This should cause some amusement among those who remember
that an Apple employee viciously flamed me here last year for my suggestion
that Apple should decommission all the low-memory globals over the space of
a year.  Don't worry, I don't expect an apology.
-- 
Tim Maroney, {ihnp4,sun,well,ptsfa,lll-crg,frog}!hoptoad!tim (uucp)
hoptoad!tim@lll-crg (arpa)