Resetting variables at end of lisp routine
Accepted solution
@Anonymous wrote:
....
My policy is not to override any existing AutoCAD commands with new defun command unless you really want to.
....
Change to:
(defun C:REVCLOUD1 (/ *error* CLAY OSM CMD SNP)
....
I was going to suggest that you can UNDEFINE the native command, and define your own under the original name. The benfit of doing so is that you don't always need to type in the full command name as you've defined it, because even menu icons [as long as they call for the command name without a period prefix] and command aliases will call up your new definition of it. This would be the approach:
(command "_.undefine" "REVCLOUD")
(defun C:REVCLOUD (....
And then, if for some reason you do want to use the native command, for example to draw one on a different Layer than the one automatically set by your new definition, or with Snap left on, you can use the period prefix to get at it:
.REVCLOUD
Usually, that native command is invoked that way somewhere within the new definition, which will typically just add stuff around it [Layer setting, System Variable settings, resettings of those, etc.]. And I've used that approach for a few things, such as the PasteBlock command that forces you to give the resulting Block a meaningful Block name in place of the usual "A$C2B2D5D64" kind of thing, recently brought up in this thread.
BUT I find that in this particular case, that doesn't work! Once it's been undefined, trying .REVCLOUD or _.REVCLOUD returns an unknown-command error, just as trying the plain un-prefixed REVCLOUD command does, whether manually at the Command: prompt or in a (command) function. So apparently REVCLOUD is a horse of a different color from most native commands. I thought maybe it was an Express Tool, but it's not, although I think it was originally, but was made "native" a long time ago. I can only assume something of that distinction has "survived" its importing into the "native" program, some things seem to be more "native" than others, and apparently even though Undefine works on something, that doesn't necessarily mean it's going to be usable in its native form with that period prefix. So always test before incorporating something like this into a (defun) or macro or Script.
Kent Cooper, AIA 
@ВeekeeCZ wrote:
.... (defun *error* (errmsg) ;runs automatically if error or ECS (if (not (wcmatch errmsg "Function cancelled, quit / exit abort, console break")) (princ (strcat "\nError: " errmsg))) ....
One thing you should change:
There should be no spaces after the commas in the (wcmatch) pattern string:
(if (not (wcmatch errmsg "Function cancelled,quit / exit abort,console break"))
The way (wcmatch) uses comma-delimited strings, it's looking for what's separated by commas to be complete and exact string possibilities. The kind of error that's going to send "quit / exit abort" as an error message is not going to include a space at the beginning of that, so as you have it, that message will not be bypassed as intended.
Kent Cooper, AIA