Old LISP file no longer works in new AutoCAD

Old LISP file no longer works in new AutoCAD

AWVGPeyton
Enthusiast Enthusiast
1,154 Views
10 Replies
Message 1 of 11

Old LISP file no longer works in new AutoCAD

AWVGPeyton
Enthusiast
Enthusiast

I have an old LISP file from 2004 which has not worked in AutoCAD for a few new versions. I would like to get it back in working order. 

The routine cleans up intersections after making a selection. I have attached the LISP file. If anyone can tell me how to make this file work again it would greatly be appreciated. I am now using AutoCAD2020 w/Toolsets.

 

Thanks in advance

0 Likes
Accepted solutions (1)
1,155 Views
10 Replies
Replies (10)
Message 2 of 11

fatal.error
Advocate
Advocate

How about the attached TRIMIT3.lsp?

Credits to Peter Jamtgaard @ AUGI.

0 Likes
Message 3 of 11

Kent1Cooper
Consultant
Consultant

Post an image or small sample drawing file showing the kind of situation in which you would use it, "before" conditions, and what you intend as "after" conditions.

 

What does "has not worked" mean?  How far does it get?  Are there any messages?  Etc., etc.

Kent Cooper, AIA
0 Likes
Message 4 of 11

AWVGPeyton
Enthusiast
Enthusiast

That is the same LISP file I am talking about.

I renamed it AT for ease of typing in the command

0 Likes
Message 5 of 11

AWVGPeyton
Enthusiast
Enthusiast

In older versions of AutoCAD I could make a selection set and the LISP file would automatically clean up the intersection lines. See the attached before & after.

Now in the newer versions of AutoCAD when I make my selection set, it now asks me for break points.

0 Likes
Message 6 of 11

AWVGPeyton
Enthusiast
Enthusiast

Still no solution. I figure I would try one more time. Can anyone help me get this LISP to work again?

0 Likes
Message 7 of 11

Patchy
Mentor
Mentor

Worth a try, turn off all snap.

Because with snap on it did not work for me.

 

snap off.JPG

 

0 Likes
Message 8 of 11

Kent1Cooper
Consultant
Consultant
Accepted solution

Remove [or comment out] the line that says just "F".  Apparently it is a change since earlier versions that now, when you feed a Break command an entity name rather than picking a point, it automatically goes into First-point mode, so that should not be explicitly called for, and the "F" is resulting in an invalid-point error [the answer to my last question in Message 3].  It worked for me in very quickie trial, with and without Osnap turned off.

Kent Cooper, AIA
0 Likes
Message 9 of 11

AWVGPeyton
Enthusiast
Enthusiast

with snap on or off the LISP still does not work.

Not sure what to do. Thank you for trying to help!

0 Likes
Message 10 of 11

AWVGPeyton
Enthusiast
Enthusiast

Removing the "F" worked!!!

 

Thank You so Much!!!!

 

Been trying to get this to work again for a LONG time!!!

 

Greatly Appreciated!!!

0 Likes
Message 11 of 11

cadffm
Consultant
Consultant

and add one (princ) line,

this underpress the "nil" at the end of AT/Trimit3 tool.

CADffm_0-1675185683246.png

 

Sebastian

0 Likes