Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!spool.mu.edu!mips!bridge2!jarthur!ucivax!orion.oac.uci.edu!nntpsrv
From: bdugan@teri.bio.uci.edu (Bill Dugan)
Newsgroups: comp.sys.mac.programmer,fa.think-c
Subject: GetNextEvent beeps at me instead of returning keyDown
Summary: This has got to be a really stupid problem
Message-ID: <28115A68.6279@orion.oac.uci.edu>
Date: 21 Apr 91 09:24:56 GMT
Organization: University of California, Irvine
Lines: 21
Nntp-Posting-Host: teri.bio.uci.edu

I'm tearing my hair out over this one.  I'm writing a Think C application 
that uses the stdio functions.  In my event loop, it returns a mouseDown
correctly, and I can drag windows, choose menu items, etc.  But when I
hit a key, it just beeps at me.  GetNextEvent doesn't even take the
"case keyDown"; it just keeps cycling over and over waiting for an event.
I'm calling GetNextEvent(everyEvent,&myEvent) the same way I do in every
other program I've ever written, but this code is a couple of years old
and converted from a Think C 3.0 project.  The code did work under 3.0.
(I've since deleted that project and started a new one just in case it was
a corrupted project file, but no dash, same problem.  I have the same bug,
incidentally, under both System 6.0.7 and 7.0b4.)

Is there some kind of call I might inadvertently have made that will mask
out the keyDown event?  Or perhaps GNE thinks that the stdio window is a
DA window and attempts to take care of the event itself instead of returning
it to me?

Puzzled,

bill
(thanks in advance!)