EndCommand Event

Triggered immediately after a command completes.

See Also | Example




An object expression that evaluates to a valid container object. In this case, the only valid container is the application.


The name of the command that was issued.


The EndCommand event follows the BeginCommand event after AutoCAD completes processing the command. If the user cancels out of the command, the EndCommand event will not be triggered.

The BeginCommand event will be fired for any basic AutoCAD command, or any command registered on the AutoCAD command stack via an ObjectARX application, or the Visual LISP vlax-add-cmd function. It will not be fired for any normally defun'd C: LISP function because it is not exposed to the command stack, even though you execute it from the AutoCAD command Line. If you need LISP commands to be recognized when they execute, you will need to use the Visual LISP vlax-add-cmd function to register the command correctly to the AutoCAD command stack.

If you undefine an AutoCAD command and then redefine it via a LISP defun, the BeginCommand event may not be triggered until an actual AutoCAD command is called; for example, (command "_.LINE" ...).

AutoCAD commands are stored in groups in the command stack. One instance of the command stack is created per AutoCAD session. This stack consists of the native AutoCAD commands, as well as any custom commands you add to it.

No events will be fired while a modal dialog is being displayed.