Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!kuhub.cc.ukans.edu!2fmlcalls
From: 2fmlcalls@kuhub.cc.ukans.edu
Newsgroups: comp.sys.mac.programmer
Subject: Re: Game input -- Bypassing GetNextEvent
Message-ID: <1991May1.030929.30240@kuhub.cc.ukans.edu>
Date: 1 May 91 08:09:29 GMT
References: <10219@etsu.CMI.COM>
Organization: University of Kansas Academic Computing Services
Lines: 25

In article <10219@etsu.CMI.COM>, davet@cmi.com (David Temkin) writes:
> Anyway, I'm interested in hearing people's experiences with these issues. 
> How do other games out there handle these problems? What are the 
> consequences/techniques for bypassing the event manager altogether? 
> Although I don't intend this game to be a very "cooperative" (windowing) 
> application, I would like to ensure that it at least does not crash or 
> cause any other serious problems under Multifinder and System 7. 
> Suggestions?
> 
> David Temkin
> Center for Machine Intelligence, EDS Corp.
> davet@cmi.com

I encountered the same problems.  I took the don't-call-WNE-just-GetKeys-
and-GetMouse approach for the same resons you mentioned.  I too am bothered by
this approach.  I didn't do it out of arrogance, but because I know of no other
way.  And besides - games are exceptions :).

I can tell you that the method seems to work sans hitch under System 7 and
MultiFinder as well.  Unless someone with more experience can straighten us out
(?) I've found you can safely use this method.

john calhoun
'when we find what we want then who will turn out the light?'
r.e.m.