Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!helios.ee.lbl.gov!ux5.lbl.gov!beard From: beard@ux5.lbl.gov (Patrick C Beard) Newsgroups: comp.sys.mac.programmer Subject: Re: Pyro Message-ID: <6277@helios.ee.lbl.gov> Date: 25 Jul 90 18:51:59 GMT References: <43256@apple.Apple.COM> Sender: usenet@helios.ee.lbl.gov Reply-To: beard@ux5.lbl.gov (Patrick C Beard) Organization: Berkeley Systems, Inc. Lines: 20 X-Local-Date: 25 Jul 90 11:51:59 PDT In article <43256@apple.Apple.COM> keith@Apple.COM (Keith Rollin) writes: #In article hairston@henry.ece.cmu.edu (David Hairston) writes: #>[lim@iris.ucdavis.edu (Lloyd Lim) writes:] #>[] I am writing an app that I want to be as MultiFinder friendly as possible. #>[] Therefore, when I call WaitNextEvent with a sleep value of 0xFFFFFFFF (the #>[] app doesn't run on Systems with the sleep bug). Unfortunately, I noticed #> #I think that what Lloyd is running into is the problem where MultiFinder #doesn't think that anyone needs time to run, so it just spins its gears #until it's time to handle an event or wake up an application. This is exactly what is going on. I have seen this before. The problem seems to be that Multifinder doesn't call SystemTask() from within this idle time. It should. I hope system 7 has a better scheduler. -- ------------------------------------------------------------------------------- - Patrick Beard, Macintosh Programmer (beard@lbl.gov) - - Berkeley Systems, Inc. "..............Good day!" - Paul Harvey - -------------------------------------------------------------------------------