Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!kth.se!cyklop.nada.kth.se!news From: d88-jwa@byse.nada.kth.se (Jon W{tte) Newsgroups: comp.sys.mac.programmer Subject: Re: Game input -- Bypassing GetNextEvent Message-ID: Date: 3 May 91 08:11:41 GMT Article-I.D.: byse.D88-JWA.91May3101138 References: <1991May1.030929.30240@kuhub.cc.ukans.edu> <12874@pt.cs.cmu.edu> <12888@pt.cs.cmu.edu> Sender: news@nada.kth.se (Mr News) Organization: Royal Institute of Technology, Stockholm, Sweden Lines: 24 In-reply-to: hairston@henry.ece.cmu.edu's message of 2 May 91 18:33:03 GMT In article <> hairston@henry.ece.cmu.edu (David Hairston) writes: MBarHeight = saveMBH. the benefit here is that you allow background [] tasking by calling WNE regularly. so why not do it this way? Hey, they're talking action games... well, my gut response is that action games should still be cooperative. if you find that you cannot run action game x because you're doing too much background processing then the user should voluntarily stop the bg applications. i think this is preferred to the alternative of having action game x unilaterally stop the bg apps. cooperative multitasking requires cooperation! The problem with this is that WNE is pretty slow even if there are no other background apps that want time. There's a lot of overhead involved, and to get decent speed on a classic or LC... Maybe an option ? -- Jon W{tte h+@nada.kth.se - Power !