Jump to content

Recommended Posts

Posted

I have tried to load all my lisps in the acaddoc.lsp file and some of them run but others don't. When i use appload for the ones that don't they then run fine.

 

Anyone any ideas????

 

This is what i use to load the lisp, I presume it's not case sensitive.

 

 
(load "T:\\Drawing Tools\\AutoCad - WARNING - Do Not Modify\\PFS.lsp")

Posted

Do all the "DEFUN C:" have unique names? In other words, no program is being overridden by another?

Posted

yeah, i checked that. I had them loadad in a combined file through the Appload suite but I've removed that.

Posted
yeah, i checked that. I had them loadad in a combined file through the Appload suite but I've removed that.

 

woodman78,

 

Even if you are loading thru acaddoc.lsp, You still need to be certain that your programs & dcl's are in the acad support search path.

I am using this method now as well and found that programs especially with dcl need to have the search path called in the options.

 

Give this a check and see what happens.

The Buzzard

Posted

Buzzard,

I tried this but no joy. I have been moved over to 2010 in the last few days. Should i be putting the following:

 

 

(load "T:\\Drawing Tools\\AutoCad - WARNING - Do Not Modify\\PFS.lsp")

 

in the acad2010doc.lsp There is no acaddoc.lsp Any ideas?

Posted
Buzzard,

I tried this but no joy. I have been moved over to 2010 in the last few days. Should i be putting the following:

 

 

(load "T:\\Drawing Tools\\AutoCad - WARNING - Do Not Modify\\PFS.lsp")

 

in the acad2010doc.lsp There is no acaddoc.lsp Any ideas?

 

 

You create your own acaddoc.lsp You name it just that way.

Make sure that this file is in the ACAD Support Search Path.

 

AutoCAD will find it and run it when you start acad.

 

Attached is an example of an ACADDOC.lsp I use on my system.

It sets the listed variables, Sets the layer to 0, Zooms to extents and loads one lisp file on every drawing I open.

 

Do not edit the acad2010doc.lsp, Its not the same thing.

ACADDOC.lsp

Posted

Even if you are loading thru acaddoc.lsp, You still need to be certain that your programs & dcl's are in the acad support search path.

 

Not really. You can load a file by specifying the full path.

 

There is nothing wrong with the location being included in the support file search path, but it's not required.

Posted
I have tried to load all my lisps in the acaddoc.lsp file and some of them run but others don't. When i use appload for the ones that don't they then run fine.

 

Anyone any ideas????

 

Yes.

 

At the top of your acaddoc.lsp file, include something like this...

 

(princ "loading acaddoc.lsp....")

 

Then at the bottom of the file, put something like this...

 

(princ "....load complete\n")

 

Then when you start AutoCAD or start a drawing, you should see the first message as the file is loaded. As soon as the file loading is complete, you will see the second message. If you never see the second one, you know something is broken in the file, because the lisp interpreter will stop loading the file when it encounters an unhandled error.

Posted
Not really. You can load a file by specifying the full path.

 

There is nothing wrong with the location being included in the support file search path, but it's not required.

 

I agree in the case where there is only a lisp file involved. When you are using a dcl, The path in the acaddoc means nothing unless you specify it Support Search Path in options.

 

I have already tested this out.

 

By the way rkmcswain,

 

Thanks for all the info concerning the acaddoc. I now use this instead of Appload or the Start-Up Suite and it works flawless. You can also do much more than just load lisps.

Posted
I agree in the case where there is only a lisp file involved. When you are using a dcl, The path in the acaddoc means nothing unless you specify it Support Search Path in options.

 

That is still a bit misleading. Why? Because LSP files can specify DCL files in any location. If the path is hardcoded in the lisp file, then that path does NOT have to be part of the support file search path.

 

Basically, the support file search path is where AutoCAD looks for any file (LSP, DCL, PGP, DWG, etc) when it can't find that file in the current directory or the drawing directory.

 

By the way rkmcswain,

 

Thanks for all the info concerning the acaddoc. I now use this instead of Appload or the Start-Up Suite and it works flawless. You can also do much more than just load lisps.

 

Thanks to you. I'm glad you investigated it and decided this was best for you. It's all we have used for a long time now.

Posted
That is still a bit misleading. Why? Because LSP files can specify DCL files in any location. If the path is hardcoded in the lisp file, then that path does NOT have to be part of the support file search path.

 

Basically, the support file search path is where AutoCAD looks for any file (LSP, DCL, PGP, DWG, etc) when it can't find that file in the current directory or the drawing directory.

 

 

 

Thanks to you. I'm glad you investigated it and decided this was best for you. It's all we have used for a long time now.

 

If a path is specifed for the dcl in the lisp, Then there should be no problem loading a dcl program thru the acaddoc. Myself like many other do not specify paths for such as the may be different between users machines and would put a limit as to where you can place them if someone did not now how to edit the lisp to get around this issue.

 

For the most I always keep both files together and enter the path in the options under the files tab. Most lisps I use day to day are all in the same directory with this same path. As far as loading the lisp, I think this is a great way to do it just the same. Where dcl is concerned, You need to consider using the path if its not specified in your program.

 

In any case I see benifits to the acaddoc.lsp that outweigh the start-up suite. Its all good.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...