Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: best way to detect command-. interrupt?
Keywords: Think C command period interrupt
Message-ID: <33392@ucbvax.BERKELEY.EDU>
Date: 28 Dec 89 16:17:58 GMT
References: <694@nems.dt.navy.mil>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 17

In article <694@nems.dt.navy.mil> science@nems.dt.navy.mil (Mark Zimmermann) writes:
>What is the 'officially approved' way to sense a command-period
>(cmd-.) so that a user can interrupt a long operation from the keyboard?

The best way is to run your event handler, so that other applications can
run, and your other windows will update while you are calculating.

Assuming you don't wish to do _that_, many people do a GetKeys(), and look
for the command and period in the resulting binary key map. This technique
may have internationalization problems, so make sure to put the bits you
are checking into a resource and let your tech support people know how to
customize it.


--- David Phillip Oster            --  No, I come from Boston. I just work
Arpa: oster@dewey.soe.berkeley.edu --  in cyberspace.
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu