Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cwjcc!gatech!ncar!tank!eecae!cps3xx!rang From: rang@cpsin3.cps.msu.edu (Anton Rang) Newsgroups: comp.sys.mac.programmer Subject: Re: Programming menus Message-ID: <3322@cps3xx.UUCP> Date: 6 Jun 89 21:49:24 GMT References: <1378@marvin.Solbourne.COM> <2005@husc6.harvard.edu> <23163@srcsip.UUCP> Sender: usenet@cps3xx.UUCP Reply-To: rang@cpswh.cps.msu.edu (Anton Rang) Organization: Michigan State University, Computer Science Dept. Lines: 26 In-reply-to: mnkonar@manyjars.SRC.Honeywell.COM's message of 6 Jun 89 19:18:02 GMT In article <23163@srcsip.UUCP> mnkonar@manyjars.SRC.Honeywell.COM (Murat N. Konar) writes: 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. 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). No, still wouldn't work. Suppose I have SuitCase II open. I hit command-O (or whatever, I think that's one of the command-key combinations). That's in the menu bar 'cause it means "Open". Now the DA gets very confused because it was running in a modal dialog. You could try to hack this by checking the window list, but it gets awfully complicated.... +---------------------------+------------------------+ | Anton Rang (grad student) | "VMS Forever!" | | Michigan State University | rang@cpswh.cps.msu.edu | +---------------------------+------------------------+