R14 Autolisp Routine Update to 2009LT

[gsksun4]

Can a lisp routine used back in AutoCad Release 14 be updated to be used in 2009LT? It's for :This Inserts An Outlet Symbol" in an acad.lsp file I have. Someone from the beginners forum suggested I try this here. I know nothing about autolisp however. Any help appreciated, thank you.

Glenn

USA

[Lee Mac]

Hmmm... you will struggle with this one... LT cannot run LISP without an extender which would set you back a bit.

[gsksun4]

Hmmm... you will struggle with this one... LT cannot run LISP without an extender which would set you back a bit.

 

Thank you for the quick reply. I thought it might be a stretch, but it was worth a try. Any idea how much the extender is and do you know it would work?

Thanks again.

[The Buzzard]

Thank you for the quick reply. I thought it might be a stretch, but it was worth a try. Any idea how much the extender is and do you know it would work?

Thanks again.

 

 

Here is a link with information:

http://www.cadopolis.com/autocad_addons/DRCauto_LT-Toolkit.shtml

[gsksun4]

Here is a link with information:

http://www.cadopolis.com/autocad_addons/DRCauto_LT-Toolkit.shtml

Thank you for the information. The toolkit costs almost as much as the 2009LT upgrade.

Thanks again.

[The Buzzard]

Thank you for the information. The toolkit costs almost as much as the 2009LT upgrade.

Thanks again.

 

Not sure how much the 2009LT upgrade is, But LT is not that expensive to start with. When you add lisp capabilities to it I am sure it will offset any costs for the price of the software package.

 

Sound like its worth it.

[ReMark]

Can the routine you speak of be handled with a macro?

[eldon]

I don't think that the routine needs to be updated. I am using routines that were originally written for r10.

[gsksun4]

I don't think that the routine needs to be updated. I am using routines that were originally written for r10.

The upgrade from 2006LT to 2009LT was $400. The extender tool kit is almost that amount and the company won't shell out for that too.

It's that bad economy thing.

[gsksun4]

Can the routine you speak of be handled with a macro?

 

The attached LISP file contains 17 "This Inserts a Outlet" commands scrolled about 3/4 of the way down the list. The language is new to me and I'm still dizzy from that last macro we did.

Glenn

 

Sorry, I had trouble with that attachment. It's on the next page.

[gsksun4]

Here is the attached LISP file.

ACAD.LSP

[Lee Mac]

You could certainly create a macro from those "insert" LISPs:

 

^C^C-insert;U2;\;;;

 

Or something similar, depending on the block and how many pauses you need.

 

^C^C = cancel last command, or any active commands

-insert = invoke insert command

; = same as hitting enter, equivalent to a space also.

\ = pause for user input.

 

This should get you started at least

 

Lee

[gsksun4]

You could certainly create a macro from those "insert" LISPs:

 

^C^C-insert;U2;\;;;

 

Or something similar, depending on the block and how many pauses you need.

 

^C^C = cancel last command, or any active commands

-insert = invoke insert command

; = same as hitting enter, equivalent to a space also.

\ = pause for user input.

 

This should get you started at least

 

Lee

 

That's a great start. So much apprciated. Now If I can work my macro trick. I'll report back on this.

Again, thank you.

[gsksun4]

That's a great start. So much apprciated. Now If I can work my macro trick. I'll report back on this.

Again, thank you.

 

Well, it took some doing, but it works. Thanks to all, especially LeeMac and ReMark.

The only down side is that I'll have a toolbar with 17 commands. That and creating the tool buttons. Too bad they don't have a text tool in that button edit window.

 

 

A little snag. Here's the macro: ^C^c-insert;D1;S;\;;;. This allows for a prompt of one attribute field. D1 is the block and S prompts for scale. Rotate comes up automatically. Don't know how to edit the macro to prompt for more than one attribute field.

[Lee Mac]

Happy to help

 

Could you not just add a few more pauses to the macro?

 

^C^C-insert;D1;S;\;\;\;

 

or something similar (play around with it!)

 

You may need to check the value of ATTREQ to make sure that the command prompts for Attributes.

 

Lee

[gsksun4]

Happy to help

 

Could you not just add a few more pauses to the macro?

 

^C^C-insert;D1;S;\;\;\;

 

or something similar (play around with it!)

 

You may need to check the value of ATTREQ to make sure that the command prompts for Attributes.

 

Lee

Actually, the block is an existing one used by the old LISP routine. The atribute fields (2) are already in the block. I"m not sure anything in the macro prompts for the attribute fields. Don't know, I'm having trouble with this one. I've alrady created the first 4. D1, U1, L1, and R1. The D, U, L, R stand for down, up, left and right. They're outlet locations. Triangles pointing in these directions. The ! stands for 1 attribute field. I'll press on.

[gsksun4]

Actually, the block is an existing one used by the old LISP routine. The atribute fields (2) are already in the block. I"m not sure anything in the macro prompts for the attribute fields. Don't know, I'm having trouble with this one. I've alrady created the first 4. D1, U1, L1, and R1. The D, U, L, R stand for down, up, left and right. They're outlet locations. Triangles pointing in these directions. The 1 stands for 1 attribute field. I'll press on.

 

 

Well, guess what? Mission accomplished!!! What a great feeling. LeeMac, I thank you so very much for all the help and support. You just made my work day a lot easier and productive. +, it's a real learning experience.

Thanks to all the rest who helped as well.

Glenn

USA

[Lee Mac]

I'm glad you got it sorted and that I could be of some assistance

 

With macros, just think about what the user would have to type at the command line if he/she were to do the same thing as the macro, and you can't go wrong

 

Lee

[gsksun4]

I'm glad you got it sorted and that I could be of some assistance

 

With macros, just think about what the user would have to type at the command line if he/she were to do the same thing as the macro, and you can't go wrong

 

Lee

 

I have everything documented and filed away.

Thanks again and have a great day.

Glenn

USA