Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!hal!nic.MR.NET!srcsip!manyjars!mnkonar
From: mnkonar@manyjars.SRC.Honeywell.COM (Murat N. Konar)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Programming menus
Message-ID: <23163@srcsip.UUCP>
Date: 6 Jun 89 19:18:02 GMT
References: <1378@marvin.Solbourne.COM> <2005@husc6.harvard.edu>
Sender: news@src.honeywell.COM
Reply-To: mnkonar@src.honeywell.com (Murat N. Konar)
Organization: ipd
Lines: 23

In article <2005@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
[in reference to a previous posting suggesting that the keyboard input
 mechanism handle MenuKey equivalents]
>	It's conceivable that you may not want Command-key keystrokes to be
>equivalenced to menu commands, but instead stand for something else. One such
>example is Suitcase II, which uses command-key equivalents for dialog box
>controls; or the Standard File package,  which uses Command-Period to
>put away the dialog...


Implementing the keyboard input mechanism as suggested (so that a menu key
equivalent causes a mouse down in menu bar/menu select returns appropriate
values) wouldn't prevent using command keys as you suggest.  The menu data
structures could be searched when a command key press is detected by the 
system.  If the key is found in a menu, treat it as a menu key equivalent,
otherwise report the key down event to the application (or DA or whatever).

   

____________________________________________________________________
Have a day. :^|
Murat N. Konar        Honeywell Systems & Research Center, Camden, MN
mnkonar@SRC.honeywell.com (internet) {umn-cs,ems,bthpyd}!srcsip!mnkonar(UUCP)