With this in mind, the use of LM: has no other meaning than identification as a function from my library, and to decrease the probability that a function of the same name will be defined within the same namespace.įor example, if I were to define a function such as: (defun AddLine ( pt1 pt2 ) Press F1 for help.įor the function to be evaluated, the user would instead need to type: (test). Typing test at the AutoCAD command-line would result in the error message:Ĭommand: test Unknown command "TEST". If the function was instead defined as: (defun test ( ) Here, typing test at the AutoCAD command-line would cause Hello World! to be printed on a new line in the command-line window. The use of the c: prefix in the function name means that the function may be evaluated as a command directly at the AutoCAD command-line. When defining a function in AutoLISP, the only naming convention which imparts an alternative behaviour on the resulting function is the prefix c: Why is the local variable ss being accessed with "LM:ss->"? "Ref" does not seem to be defined so it seems it must be part of the system somehow although I could not pull out any documentation describing such use of "Ref->". The use of "Ref->" is also a question for me. I am trying to get some explanation of what "LM:" actually means. This is the first time I have seen this type of syntax being used in AutoLISP. (vla-item (vla-get-Blocks doc) (cdr (assoc 2 (entget block)))) (vla-CopyObjects doc (LM:SafearrayVariant vlax-vbobject lst) (foreach obj lst (vla-transformby obj mat)) Mat (vlax-tmatrix (append (mapcar 'append (car mat) (mapcar 'list (cadr mat))) '((0. (defun LM:AddObjectstoBlock ( doc block ss / lst mat ) Adds all objects in the provided SelectionSet to the
0 kommentar(er)
