Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!unmvax!ariel.unm.edu!nmsu!opus!ogden From: ogden@nmsu.edu (Bill Ogden) Newsgroups: comp.sys.mac.programmer Subject: Re: Copybits & GetNextEvent questions.. Message-ID: Date: 27 Nov 90 19:29:05 GMT References: <1990Nov26.184013.6464@daffy.cs.wisc.edu> <1990Nov26.193032.17934@ux1.cso.uiuc.edu> Sender: news@NMSU.Edu Organization: NMSU Computer Science Lines: 30 In-reply-to: dorner@pequod.cso.uiuc.edu's message of 26 Nov 90 19:30:32 GMT In article <1990Nov26.193032.17934@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: > 2. I am writing an arcade game for the Mac ( for the past four months..) > and I was wondering if there is anything wrong with NOT fetching events. I'd strongly suggest you look for events at least "once in a while". Doing the necessary stuff every second or two shouldn't be that big a burden. This will solve the "menu" problem for you. More importantly, your game will give time to background applications, which is very important. -- Does this mean that a good way to prevent other processes from robbing time from your time critical programs is to use GetKeys? Does this prevent even the operating system to steal time from your program? How is GetOSEvent different? No flames please, but I would like to write a progam that gets a keystroke *as soon* as it occurs, and I am concerned that the operating system may be off doing something that I don't care about. Is there a way of making sure? Bill Ogden ogden@nmsu.edu -- ogden@nmsu.edu Bill Ogden Computing Research Lab New Mexico State University Las Cruces, NM