Xref: utzoo comp.sys.mac:14243 comp.windows.misc:357
Path: utzoo!mnetor!uunet!izimbra!dsc
From: dsc@izimbra.CSS.GOV (manic pop thrill)
Newsgroups: comp.sys.mac,comp.windows.misc
Subject: many things you wanted to know about multifinder but were ...
Message-ID: <9504@uunet.UU.NET>
Date: 21 Mar 88 17:59:46 GMT
References: <4129@hoptoad.uucp> <283@rhesus.primate.wisc.edu> <1710@ssc-vax.UUCP> <1174@cpocd2.UUCP> <7721@apple.Apple.Com>
Sender: usenet@uunet.UU.NET
Organization: the levi stubbs' appreciation society
Lines: 17
Keywords: window human computer interface
Summary: check out the recent byte article on multifinder

In article <7721@apple.Apple.Com> lsr@Apple.COM (Larry Rosenstein) writes:
>In article <1174@cpocd2.UUCP>, howard@cpocd2.UUCP (Howard A. Landman) writes:
>> 
>> Under MultiFinder, each program (except possibly the last one) must be
>>specially coded to be "MultiFinder compatible" by calling WaitNextEvent
>>instead of GetNextEvent (if I don't have them reversed).
>
>Not true.  WaitNextEvent exists only to more effectively use the CPU.
>GetNextEvent can cause a context switch as well.

a couple of months ago, `byte' had an article on `multifinder' which i
thought was very helpful in understanding `multifinder' issues
including getnextevent/waitnextevent.  i think it was in the december
or january issue, but don't hold me to that.  the article in question
was the most (um first? :-) useful `byte' article i had read in ages.

dsc