Path: utzoo!attcan!uunet!samsung!usc!apple!keith From: keith@Apple.COM (Keith Rollin) Newsgroups: comp.sys.mac.programmer Subject: Re: Pyro Message-ID: <43256@apple.Apple.COM> Date: 23 Jul 90 00:33:08 GMT References: Organization: Apple Computer Inc, Cupertino, CA Lines: 23 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 > >umm, i seem to recall a tech note (sorry i don't remember the number but >you could check the sumex archives, info-mac/apple/tn) that stated that >the largest sleep never exceed 50L for empirically derived reasons. >perhaps that is the source of your problem? I think that this was a MultiFinder 1.0 bug that's since been fixed (and that this is what Lloyd is referring to as the "sleep bug"). 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. -- ------------------------------------------------------------------------------ Keith Rollin --- Apple Computer, Inc. --- Developer Technical Support INTERNET: keith@apple.com UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith "Argue for your Apple, and sure enough, it's yours" - Keith Rollin, Contusions