Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

Macros to control alias; can't find

Anonymous

Macros to control alias; can't find

Anonymous
No aplicable

My company just got me a new laptop.  And I've contacted AutoDesk to assist with migrating over the software, license and environment.  For the most part, everything looks and runs the same.  However, I had a custom alias that someone helped me set up (ZZ) which performs the functions of Zoom, Extent, Zoom .8X all in a single alias command.  I can't remember how it was done or how to repeat it.  And it didn't come over with the migration.  It seems like a small thing but I use this command all the time.  It's driving me nuts.  Anyone who could help?

0 Me gusta
Responder
Soluciones aceptadas (1)
555 Vistas
9 Respuestas
Respuestas (9)

pendean
Community Legend
Community Legend
It was probably a custom lisp file(s): you will need to find it on your old PC/Laptop and move it manually. AutoCAD migration tools aren't designed to capture personal added content very well.

Anonymous
No aplicable

Is there a command that allows me to see a list of all the lisps available?  Maybe a folder that holds them?

0 Me gusta

Kent1Cooper
Consultant
Consultant

@Anonymous wrote:

Is there a command that allows me to see a list of all the lisps available?  Maybe a folder that holds them?


You should keep them in some logical, designated and known location, but if you haven't, you can put  *.lsp  in the Windows Explorer Search window.

Kent Cooper, AIA

Anonymous
No aplicable

Okay, I found the custom LISP.  I took it from the same folder on the old computer to the new one.  However, when I type ZZ on the command line it doesn't recognize this command.  How do I activate the lisp?  ZZ is not in the list of aliases so clearly it's not an alias that performs the routine.  What else could have been used?  As I said, it's been a long time.

 

Thanks,

Jim 

0 Me gusta

pendean
Community Legend
Community Legend
You also need to find your ACADDOC.LSP file that autoloads that lisp in AUtoCAD.
PLUS
The "folder" needs to be listed in AutoCAD as a searchable path: OPTIONS command, FILES tab, add it to the SUPPOR FILE SEARCH PATH section.

Anonymous
No aplicable
Solución aceptada

All set.  Had to run the APPLOAD command and add the lisp to the list that needs loaded when AutoCAD loads.  

 

Thanks to everyone for your help!

 

 

0 Me gusta

Kent1Cooper
Consultant
Consultant

It could have been defined in a file that was automatically loaded into every drawing when you opened it, by an acaddoc.lsp file.  Search for that, and if there is one, it may have a (load) or (autoload) function in it that loaded the .lsp file in question.  If you copy that acaddoc.lsp file into some folder location that's in the Support File Search Path list in OPTIONS in your newer setup, it will do the same.  In any case, you can go into APPLOAD, navigate to where you put that file, and Load it yourself.

Kent Cooper, AIA

Anonymous
No aplicable

Yes, that was exactly the issue.  All set now.  Thanks again.

0 Me gusta

Kent1Cooper
Consultant
Consultant

@Anonymous wrote:

....  Had to run the APPLOAD command and add the lisp to the list that needs loaded when AutoCAD loads.  .... 


I was going to advise against doing it that way, because as I recall from many years back [and it's still described this way in Help], what's in the Startup Suite in APPLOAD would load when AutoCAD is started, but not  upon opening every drawing thereafter.  But that must have changed, because I find that now a custom definition like that, listed in the Startup Suite, does "stick" and is available in subsequently-opened drawings.  That was at least worth finding out.

 

But I have a suggestion.  Do it by way of an acaddoc.lsp file anyway, instead of the Startup Suite, and put that command-defining file into an (autoload) function [read about it in the AutoLisp Function Reference].  That way, the file defining it won't  be loaded unless  and until  you ask for that command.  So if in a given drawing session you never has a use for that command, it won't ever bother to load the file.  This approach could have a noticeable effect on drawing-opening times if [when?] you accumulate a large number of such custom commands.

Kent Cooper, AIA
0 Me gusta