undefine \ redefine AutoCAD standard commands

[Moshe-A]

Hi Guys,

Many of us here knows that one can undefine\redefine an AutoCAD standard commands but still can be invokes by using the dot prefix. lately i encounterd some applications that disbales standard AutoCAD commands totally

i mean even trying to invoke it with dot prefix. maybe it's an objectarx \ net application?

can someone here elaborate on this, can it be done with VisualLISP\ActiveX?

can a user temporary override this? (if he wants to invoke the native command)

thanks in advance

Moshe

[scot-65]

Perhaps check using ATOMS-FAMILY
then REDEFINE if not present in the
returned list of strings (using MEMBER)

???

[john.uhden]

Are you sure that they are AutoCAD commands, or maybe just command functions?

Otherwise, I don't get it.

Is the command DDATTE?

[Moshe-A]

yes i very sure

the commands are purge, textedit, ddedit

[dgorsman]

I believe it's possible in managed dotNET, where you monitor the CommandWillStart event, and veto the command.  While there is a similar reactor for LISP, I'm not certain you can actually stop the command from there.

[Moshe-A]

thank you, can a user temporary override this, if he wants to invoke the native command.

[pbejse]

---

@Moshe-A wrote:

... lately i encounterd some applications that disbales standard AutoCAD commands totally..

*Off-topic* [ related to ]

During these past two weeks, our office experience a weird behavior with Autocad 2017 [ and only in 2017 ],  native commands like Opensheetset does not work and even ctrl+4 won't even bring up the Shee Set Manager panel. and to top it off, drawing files won't even open at all.

We ended up using "Reset Settings to Default" any ideas? 

BTW: It all started when one of the users started using Autocad 2018

Appreciate any help

[dgorsman]

@pbejse - bundles would be my first thought.  While they may install from a specific version, they can be set to load in multiple versions.

[doaiena]

The "CommandWillStart" reactor in lisp can intercept a command and execute your own custom code before it, but it can't redefine/veto the command within the same event.

The AutoLisp reactor works like this:
(command "._LINE")

(Place your code here:)
(Continue execution of "._LINE")

You can also exit the current command within your code and execute another one in its place:

(defun ReactorFun (Reactor lst)

 (if (= (car lst) "LINE")
 (progn
 (vla-SendCommand (vla-get-activedocument (vlax-get-acad-object)) "(command) ")
 (alert "Execute custom command here")
 ))
)

(if (not CommandReactor)
 (setq CommandReactor (vlr-command-reactor nil '((:vlr-commandWillStart . ReactorFun))))
)

[pbejse]

---

@dgorsman wrote:

- bundles would be my first thought.  

---

Thank you dgorsman, I will look into that.