Lockup while using VLIDE

Lockup while using VLIDE

Neptune48
Enthusiast Enthusiast
1,109 Views
4 Replies
Message 1 of 5

Lockup while using VLIDE

Neptune48
Enthusiast
Enthusiast

While trying to run an AutoLISP routine in VSLIDE, AutoCAD 2016, it locks up as soon as I type the function command in to the AutoCAD command prompt.  The command line shows my typed command superimposed over a dimmed "Type a command" prompt, and the thing just sits there until I close VLIDE.

The routine used to work, but I fear I have inadvertently changed a setting or something.  It still works on AutoCAD 2019 VLIDE, but I don't want to use the shared license when I have my own stand-alone 2016 license.

 

I have been working for a week trying to find out why a routine that has run reliably for over 20 years suddenly is not running correctly, across all platforms (AutoCAD 2011 through 2019) and across both Windows 7 and Windows 10, and it is very difficult to do a step through when VLIDE does not work.

 

Any help would be appreciated.

 

Thanks,

Bruce

0 Likes
1,110 Views
4 Replies
Replies (4)
Message 2 of 5

Moshe-A
Mentor
Mentor

@Neptune48 hi,

 

i have seen this behavior numerous of times especially with reactors.

try to go back to a previous version step by step until you reach the one that works.

 

moshe

 

 

 

 

0 Likes
Message 3 of 5

Neptune48
Enthusiast
Enthusiast

Thanks for your response Moshe-A.

I ended up solving the original issue the old-fashioned way, with a text editor.  So far I have found VLIDE to be nothing but useless and frustrating.

Even after solving the issue, I tested it using VLIDE.  It worked alright, but when I finished I was able to close the windows within VLIDE but had to quit AutoCAD altogether to close the VLIDE screen. 

As far as I am concerned, VLIDE is a piece of junk.  After 30 years of using AutoCAD, even having been an ATC manager and trainer, I have found my first Autodesk product to loathe.

Regards,

Bruce

 

0 Likes
Message 4 of 5

Moshe-A
Mentor
Mentor

@Neptune48 hi,

 

sorry to hear that but i totaly disagree with you. inspite those problems i found the VLIDE a great tool and i even do not use the debug feature, it all depends on what's in the code. eventually your lisp program should run without it.

 

moshe

 

 

 

0 Likes
Message 5 of 5

Neptune48
Enthusiast
Enthusiast

I would disagree with me, too, based on the potential power of VLIDE in analyzing and debugging—if only it would actually work instead of locking up my machine all the time.

 

If I could bill for those lost hours I might have retired by now.

 

Regards,

Bruce

0 Likes