TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: 77077 on June 03, 2015, 02:17:52 AM
-
eg.
VLX name: attmodify
VLX command: am
(defun c:new_command ()
(if (not (member 'ddmodify (vl-list-loaded-vlx)))
(load "attmodify.VLX")
)
(c:am)
)
-
If the VLX was compiled to a separate namespace, you will probably need to use something like:
Otherwise, try something like:
(defun c:am
nil (c:attmodify
))
You can use vl-list-loaded-vlx to determine whether the VLX has been compiled to its own namespace, since this function should only list symbols identifying separate-namespace VLX applications.
-
If the VLX was compiled to a separate namespace, you will probably need to use something like:
Otherwise, try something like:
(defun c:am
nil (c:attmodify
))
You can use vl-list-loaded-vlx to determine whether the VLX has been compiled to its own namespace, since this function should only list symbols identifying separate-namespace VLX applications.
Hi lee, Thanks for reply.
I mean some different VLX, But have same command . so need change VLX's command.
-
I mean some different VLX, But have same command . so need change VLX's command.
You cannot modify a VLX.
-
I mean some different VLX, But have same command . so need change VLX's command.
You cannot modify a VLX.
Yes , So, I post this thread.
It's another way（Method）
eg: a.vlx & b.vlx have same command "zbbz"
I use this method
)
(C:zbbz)
)
)
)
)
(C:zbbz)
)
)
)
-
Lee, can you explain why if the vlx is compiled to a separate Namespace you nid to use sendcommand, I had some problems with a vlx that can run in one PC, but when I distribute it, it doesn´t work anymore.
Saludos
Marco Jacinto
-
Lee, can you explain why if the vlx is compiled to a separate Namespace you nid to use sendcommand, I had some problems with a vlx that can run in one PC, but when I distribute it, it doesn´t work anymore.
Hi Marco,
When working with AutoLISP, all symbols & functions are usually defined either within the document namespace or blackboard namespace (if vl-bb-set is used); in this way, all defined symbols (functions / constants / global variables etc.) defined in the namespace for one document (drawing) will be accessible by (and may also interfere with!) all other defined symbols in the same namespace, but cannot be accessed by functions defined in another namespace, e.g. in another drawing, unless a function such a vl-propagate has been used to propagate the symbol across multiple namespaces.
Hence, if a VLX is compiled to a separate namespace, all symbols & functions defined by the VLX will reside in a separate namespace (perhaps think of it like a 'container') isolated from the document & blackboard namespaces, and such functions won't be accessible by functions evaluated within the document namespace, unless either exported using vl-doc-export, or defined directly in the document namespace using the vl-doc-set function evaluated from within the VLX namespace.
Here's (http://autode.sk/I4gsdN) another brief explanation of a namespace (from an AutoLISP perspective).
Lee
-
Thanks for your response Lee.
I have always assumed that the c: functions were exported by the compiler by default, so I didn't figure out the problem when my c: functions and all others weren't exposed to the drawing, even when I explicitly exported them via vl-doc-export.
Will do some test to see if I can understand an apply the concepts
-
If the VLX was compiled to a separate namespace, you will probably need to use something like:
It looks very comfortable.
Otherwise, try something like:
(defun c:am
nil (c:attmodify
))
You can use vl-list-loaded-vlx to determine whether the VLX has been compiled to its own namespace, since this function should only list symbols identifying separate-namespace VLX applications.
Hi lee, Thanks for reply.
I mean some different VLX, But have same command . so need change VLX's command.