Separate .pgp files

[RobertB]

It would be great if we could edit/maintain a separate .pgp file for custom aliases instead of being forced to edit one of the Autodesk-installed files (Acad.pgp). That way we would avoid needless editing every time a new version came along.

[Homerloew]

Are you saying it should be set up like the custom.mnu is in 2005 where you put any and all customization into one mnu? When a new release comes along, you copy only the custom.mnu. If this is the case, I'm all for it.

[Ed Jobe]

What about where the custom.pgp conflicts with acad.pgp? Load acad.pgp first and then the custom overwrites changes made by acad.pgp, allowing only one alias per command? They would have to first check that the command doesn't have more than one alias, then check to see if that alias isn't already used by another command...could be done.

[kryptonite_186]

Sounds like a winner!!

[Glenn Pope]

What about where the custom.pgp conflicts with acad.pgp? Load acad.pgp first and then the custom overwrites changes made by acad.pgp, allowing only one alias per command? They would have to first check that the command doesn't have more than one alias, then check to see if that alias isn't already used by another command...could be done.
Why would you restrict the number of alias per command. Right now you can assign multiple alias to a command. You could have c, co, and cp start the copy command.

I like this idea. It expand the idea they started with 2005 by having a custom area at the end of the pgp file.

[RobertB]

I like this idea. It expand the idea they started with 2005 by having a custom area at the end of the pgp file.
Actually, it didn't really start with 2005, it was simply "documented" by Autodesk in 2005. Ever since there was a pgp you could simply place your desired alias definitions at the end of the file and it would overwrite definitions earlier in the file. :wink:

[lcamara]

Why would you restrict the number of alias per command. Right now you can assign multiple alias to a command. You could have c, co, and cp start the copy command.

I think he meant to say "only one command per alias".

I think this would be a good idea, too - as long as acad.pgp is loaded first, then the custom is loaded after (to redefine aliases). They could rename acad.pgp to acad2005.pgp (or whatever version) and make acad.pgp for the user (the way acad2000/acad.lsp and acad2000doc/acaddoc.lsp are).

Currently I don't even touch acad.pgp because I don't have any external commands. I put all our company aliases in acaddoc.lsp, and my personal aliases in my personal .mnl file. This allows me to distribute changes easily through our network.

[jaberwok]

Try using the pgp file. It's much simpler.
As said by others, put your aliases at the end of the alias section.

[lcamara]

Try using the pgp file. It's much simpler.
As said by others, put your aliases at the end of the alias section.
Yes, while this line of text:


CO, *COPY

is simpler than this one:


(defun C:CV () (command "COPY")(princ))

there isn't any actual difference when you consider that to create a new alias, you would just copy a line & replace the command and alias names.

Also, the advantage to using acaddoc.lsp for aliases is that you can also include simple programs and command auto-loaders all in one list. I have our shortcuts/commands/autoloaders organized by type (Draw, Modify, etc.), then alphabetically. If you're trying to change something, you don't have to try to remember if the command is an alias, or a custom command - you just look in one file.

Yes, it appears that Autodesk will migrate your settings into a new file when you upgrade. But I'm more concerned with distributing changes throughout the company, and everything is truly "much simpler" if all the custom files are independent of Autodesk's files.

When I upgraded from 2002 to 2005, all I had to do was make a copy of our menu directory, so 2005 could recompile the menus & still allow 2002 to use the old ones. Other than that, all our lisp routines, block libraries, etc. are used by both.

For us, the benefits of using the .pgp file just don't outweigh the disadvantages.