Menu/Command Table inheritance.

• To: seth@gandalf.hrl.hac.com, clim@BBN.COM
• Subject: Menu/Command Table inheritance.
• From: Scott McKay <SWM@sapsucker.scrc.symbolics.com>
• Date: Wed, 6 Nov 1991 15:39-0500
• In-Reply-To: <9111012145.AA00648@gandalf>

    Date: Fri, 1 Nov 1991 16:45 EST
    From: seth@gandalf.hrl.hac.com

    Buried in the manual I discovered that menus are not inherited by
    command tables.  Why?

Because we (Dave Moon and myself) decided that, for the most part,
inheriting the menu items wasn't usually the right thing.  Of course, we
could be wrong, but that's what we decided.

    What is the right way to define an application-frame mixin with
    a default set of commands (i.e., exit-frame) and inherit them?
    I made sure to specify the mixin in the define-application-frame
    form and I explicitly inherit the command table from the mixin
    but the menus don't inherit (as noted above) and defining a local
    menu item to access the command doesn't seem to work quite right
    either.

This all sounds right.  You used ADD-MENU-ITEM-TO-COMMAND-TABLE, right?

    Seth Goldman
    seth@gandalf.hrl.hac.com
    (213) 317-5693

0,,

• Re: Menu/Command Table inheritance.
• From: seth@gandalf.hrl.hac.com

• Menu/Command Table inheritance.
• From: seth@gandalf.hrl.hac.com

• Prev: Avoiding delete-output-record-element error
• Next: Highliting menu items
• Index: CLIM Mailing list (5-Oct-90 to 31-Dec-91)
• Thread: CLIM Mailing list Index (5-Oct-90 to 31-Dec-91)