0 Members and 2 Guests are viewing this topic.
This exact situation is one of the reasons why I attempt to use unique names for any global variables I use.All it takes is for code in a VLX or FAS that the user has no control over to use code as demonstrated with the same variable names as you and the whole lot falls down.
There is only few cases when a release is needed on visual lisp code.
How about using a protected namespace VLX.... there we don't have any problema.
(ot: good idea to obscure your team support control).
(ot: good idea to obscure your team support control).<nodding.gif>
I never learned how to do the protected namespace thing. But it's time I learned. What's the best way to get started? I read the help files and they just made my eyes glaze over.
If you need help on that... let me know Steve.I got the impression that ALL the help stuff from adesk was very clear...... [ahaaaaa]
(setq obj (vlax-ename->vla-object ename))