Newsgroups: comp.sys.mac.programmer Path: utzoo!utgpu!jarvis.csri.toronto.edu!csri.toronto.edu!dudek From: dudek@csri.toronto.edu (Gregory Dudek) Subject: Re: System 6.0 breaks my cdevs! revisited Message-ID: <8806242206.AA03399@darcy.csri.toronto.edu> Organization: University of Toronto, CSRI References: <227@hodge.UUCP> <12523@apple.Apple.COM> <4798@husc6.harvard.edu> Date: Fri, 24 Jun 88 16:46:34 EDT In article <4798@husc6.harvard.edu> fry@huma1.UUCP (David Fry) writes: >In article <12523@apple.Apple.COM> lsr@apple.apple.com.UUCP (Larry Rosenstein) writes: >> >>> Question: how do you detect MultiFinder's presence or absence under 6.0? >> >>Apple does not >>want people writing code that depends on MultiFinder being present or >>absent > >What do I do when I want a certain lengthy process to be done in >the background, so the user can switch to another applicaition >if he wants, but I want to check for the existence of >MultiFinder before wasting the extra CPU time catching events >(so I know if he switched out) and calling WNE while in >the background? As for now, I'll just have to do it all the >time. > If you do a lengthy computation without checking periodically for events, you may cause a variety of problems for DAs & spoolers even if MF isn't running. If it takes *that* long to check for events, then maybe you're looking too often. Greg Dudek -- Dept. of Computer Science (vision group) University of Toronto Reasonable mailers: dudek@ai.toronto.edu Other UUCP: {uunet,decvax,linus,pyramid, dalcs,watmath,garfield,ubc-vision,calgary}!utai!dudek ARPA: user%ai.toronto.edu@relay.cs.net