Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!apple!darin
From: darin@Apple.COM (Darin Adler)
Newsgroups: comp.sys.mac.programmer
Subject: Re: WaitNextEvent problem
Keywords: WaitNextEvent MultiFinder SystemTask
Message-ID: <1643@internal.Apple.COM>
Date: 3 May 89 08:43:34 GMT
References: <2864@crete.cs.glasgow.ac.uk> <520@biar.UUCP>
Organization: Apple
Lines: 21

In article <520@biar.UUCP> trebor@biar.UUCP (Robert J Woodhead) writes:
> In article <2864@crete.cs.glasgow.ac.uk> dunlop@cs.glasgow.ac.uk (Mark Dunlop) writes:
> > [Mark is having problems with WaitNextEvent]
> > The call was -> WaitNextEvent(EveryEvent,TheEvent,-1,nil);
> 
> Did you remember to tell the system that the application was multifinder
> friendly, etc, etc, by setting the appropriate bits in the SIZE -1 resource.
> See IM and the tech notes for details on being multifinder friendly.

Mark is doing the right things to be MF friendly.

Mark, you have found one of the known bugs in existing versions of MultiFinder.
Drivers get starved when applications pass large sleep values, because MF
only calls SystemTask to service drivers when feeding events to an application.
We had this same problem with the DTS Sample application last year, and MacApp
has the same problem. It will be fixed in a future version of MultiFinder, but
for now, passing a large sleep value has this side effect.
-- 
Darin Adler, System Software Scapegoat, Apple Computer
	Internet: darin@Apple.com
	UUCP: {nsc,sun}!apple!darin