command-enabled

• To: clim@BBN.COM
• Subject: command-enabled
• From: Chris Elsaesser <chris@starbase.mitre.org>
• Date: Mon, 18 Apr 1994 07:59:14 -0400

Clim-2-beta
Lucid 4.0.3

When I do:

  (setf (clim:command-enabled 'com-Run *frame* *control-commands*) nil)

which I thought was consistent with the doc:

"You can use setf on clim:command-enabled in order to enable or disable a command"

And:

> (describe 'clim:command-enabled)
CLIM:COMMAND-ENABLED is a symbol.  Its home package is CLIM.
Its global function definition is #<Standard-Generic-Function CLIM:COMMAND-ENABLED (1)>.
#<Standard-Generic-Function CLIM:COMMAND-ENABLED (1)> is a compiled function.
Its argument list is (COMMAND-NAME FRAME &OPTIONAL COMMAND-TABLE).

But I get:

>>Error: (:GENERIC-FUNCTION (SETF CLIM:COMMAND-ENABLED) :|dispatch code|) called with 4 arguments, but only 3 arguments are allowed

(:GENERIC-FUNCTION (SETF CLIM:COMMAND-ENABLED) :|dispatch code|):
   Required arg 0 (ARG-0): NIL
   Required arg 1 (ARG-1): COM-RUN
   Required arg 2 (ARG-2): #<Ap-Gui #X41CBB01E>
:C  0: Ignore extra arguments
    1: AP Interface top level
    2: Exit AP Interface
    3: Kill process #<Process AP GUI 41B943BE>
    4: Restart process #<Process AP GUI 41B943BE>

-> 

advice?

chris@azrael.mitre.org

• Re: command-enabled
• From: Daniel Cerys <cerys@BBN.COM>
• Re: command-enabled
• From: pchu@BBN.COM

• Prev: Re: setting the items of a list-pane
• Next: Re: command-enabled
• Index: CLIM Mailing list (1-Jun-94 to 30-Jun-95)
• Thread: CLIM Mailing list Index (1-Jun-94 to 30-Jun-95)