Topic: help leader_none.lsp

[cretu11]

Hello All,
I want to use the lisp lider_none.lsp (see attach) but can not find the correct command line to be written in acad2008doc.lsp (see attach).
Command line is written in the tags LEADER NONE to the end of acad2008doc.lsp .
The smallest help is welcome.
Respectfully.

[Chris]

I wouldnt write anything in the acad2008doc.lsp  you never know when Autodesk might change something.
I would suggest creating a file called acaddoc.lsp and placing it within the support directory.
I havent looked at any of your code, but to load it, I'd write
(load "leader_none.lsp")

[cretu11]

Hi Ghris,
By default is this acad2008doc.lsp (from installation).
I have not changed.

[Lee Mac]

http://docs.autodesk.com/ACD/2011/ENU/filesACG/WS73099cc142f4875513fb5cd10c4aa30d6b-7f72.htm

[cretu11]

Thanks Lee Mac
The solution is perfect on you .
Here is acaddoc.lsp (with a path to long dont work).

[nivuahc]

Just a bit of un-asked-for advice... if you're going to be loading routines with your acaddoc.lsp file you might want to consider doing something similar to what I do.

On our company server I have a folder structure similar to this;

Code: [Select]

P:\ACAD\
P:\ACAD\Blocks\
P:\ACAD\Profiles\
P:\ACAD\Lisp\
P:\ACAD\Lisp\ARX\

I have a block of code at the top of my acaddoc.lsp that looks something like this;

Code: [Select]

(setq RootPath (if (findfile "P:\\ACAD\\.local") "P:\\ACAD\\" "\\\\Server\\Path\\ACAD\\")
      BlockPath (strcat RootPath "Blocks\\")
      LispPath (strcat RootPath "Lisp\\")
      ARXPath (strcat LispPath "ARX\\")
      ProfilePath (strcat RootPath "Profiles\\")
)

If I've setup a local copy of our routines on a company laptop I'll map the folder as the project drive and create an empty file called .local in the ACAD folder.

Now, when I'm writing code and I want to load something I write it like this;

Code: [Select]

(defun c:MyCommand ()(load (strcat LispPath "MyRoutine")) (c:MyCommand))
This way, later on, when something gets changed (like they move all of our stuff to a different server or they decide to change the drive letter on us) all I have to do is change the path at the top of my routine. Makes it fairly easy to update lots of routines without actually having to update lots of routines...

Just my $0.02