Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!cs.utexas.edu!tut.cis.ohio-state.edu!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Programming menus
Message-ID: <2005@husc6.harvard.edu>
Date: 6 Jun 89 00:41:35 GMT
References: <1378@marvin.Solbourne.COM>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 36

In article <1378@marvin.Solbourne.COM> dce@Solbourne.com (David Elliott) writes:
>
>I would think that each menu item would have a unique identifier
>associated with it, and that the menu selection mechanism would return
>that identifier.  That way, you could modify the menu during
>development without having to recompile.  Instead, what you get back is

	Actually, that's how MacApp does it for you. I think. :-)

>
>Also, the menu key mechanism doesn't seem to be as useful as it
>might be.  I don't understand why it is necessary to call MenuKey
>to find out which menu item was requested.  Why doesn't the
>keyboard input mechanism handle this?

	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...


		--Rich



~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

 "She told me to make myself comfortable, so I pulled down my pants
 and sat in the pudding." -Emo Phillips
~~~~~~~~~~~~~~~