Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English) Newsgroups: comp.sys.mac.programmer Subject: Questions about multitasking on the mac Message-ID: <10971.282FE0A9@stjhmc.fidonet.org> Date: 13 May 91 04:44:41 GMT Sender: ufgate@stjhmc.fidonet.org (newsout1.26) Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ Lines: 25 John T. Nelson writes in a message to All JTN> I suppose this can be done but its GROSS infusing this event JTN> code in every module to get timely event updates. I can't figure JTN> out a better way unfortunately. Anyone have a different philosophy JTN> on how this could be accomplished? Do you want responsiveness to events concerning the operation of your compiler (like s and the like) or do you simply want to allow some background time? If the latter, then a call to WaitNextEvent, without processing the event, will give the background applications some time (although not much!). If you simply want to be able to cancel operations (as well as allow *some* backgrounding), simply checking for in your Do_Wait_Next_Event function would be sufficient (or so I would think). Lawson -- Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English Internet: Lawson.English@p88.f15.n300.z1.fidonet.org