CLIM command-table bug

• To: clim@BBN.COM, rwk@crl.dec.com
• Subject: CLIM command-table bug
• From: Markus Fischer <SUN4.SGER!MF%sger.uucp@BBN.COM>
• Date: Wed, 10 Jun 1992 11:47+0200
• In-Reply-To: <19920609211900.4.RWK@MULESHOE.MCC.COM>
• Reply-To: mf%sger.uucp@BBN.COM

    Date: Tue, 9 Jun 1992 23:19+0200
    From: "Robert W. Kerns" <unido!mcc.com!ai.RWK>

    Could someone please explain to me the logic of having keystrokes
    not be inherited by command tables??

    It seems to me that this renders CLIM command tables completely useless
    if you care about inheritance, and you use keystrokes.  How can it
    possibly be sane for the inheritance of keystrokes and other attributes
    to be different???

    If keystrokes were inherited, and you wanted to use a different set of
    keystrokes in some situation, define the commands in one command table,
    the keystrokes in another, and use whichever you want, depending on whether
    or not you want the keystrokes.  This is elementary object-oriented-programming
    modularity.

    No such modularity is possible if they follow different rules.

I don't know about keystrokes, because I don't use them, 
but I think menu items aren't inherited either, and I find that
quite bad, too.

Markus Fischer, MF@SGER.UUCP              Mergenthaler Allee 77-81
Consulting Services                       W-6236 Eschborn, Germany
Symbolics Systemhaus GmbH                 Phone: +49 6196 47220, Fax 481116

• CLIM command-table bug
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>
• CLIM command-table bug
• From: Scott McKay <SWM@stony-brook.scrc.symbolics.com>

• CLIM command-table bug
• From: "Robert W. Kerns" <ai.RWK@mcc.com>

• Prev: CLIM command-table bug
• Next: presentation-replace-output & clim:*command-unparser*
• Index: CLIM Mailing list (1-Jan-92 to 31-Aug-92)
• Thread: CLIM Mailing list Index (1-Jan-92 to 31-Aug-92)