Topic: CUI loading of lisp files

[nobody]

Based on what Sinc hints to at the bottom of this years ago I gather that the CUI loads the lisp files by finding them in support paths. Can anyone confirm?

https://cc.bingj.com/cache.aspx?q=path+of+lisp+files+in+cui&d=4989901676940115&mkt=en-US&setlang=en-US&w=GTShMqhrhtndJVYvx1Espm9-SFpwx--0

[tombu]

He suggested storing those lisp files where they could be found in the support path which makes loading them easier. That's how most of us store them so paths aren't required. The folder your lisp is stored should also be a Trusted Folder.

[nobody]

Thanks. I'm trying to understand if the CUI utilizes the "Full Path" for those lisp files in some way, or if it simply finding them in a support path.

[PKENEWELL]

Forgive me for chiming in, but doesn't a CUI automatically load a lisp file with the same name and an .mnl extension if found? I believe these must be in the support paths.

[nobody]

Basically trying to wrap my head around this.  The lisp file added to the CUI through the CUI command, then selecting "LISP" and loading it.

If those lisps are moved, but to a location in the support path, will they continue to work when autocad is opened again?

I was trying to see if there was a way to see if the real path was saved in the CUI somehow, but don't need to do that. Thinking about it now, I just need to create a new directory somewhere and add it to the support path, then close cad, move the lisp, then reopen cad and see if it works.

I was under thinking it hehe.

Thanks all!

[nobody]

Tested it. For anyone in the future who is interested in this it turns out the CUI does somehow store the full path of the files. Moving lisps stored in the CUI this way, even if to a support path, causes them to not load.

[Peter2]

...Moving lisps stored in the CUI this way, even if to a support path, causes them to not load.

For me, that's obvious and a standard behaviour.
a) Define only a file - and it is searched everywhere in support paths
b) define it with full path - it is only searched there and nowhere else

[nobody]

...Moving lisps stored in the CUI this way, even if to a support path, causes them to not load.

For me, that's obvious and a standard behaviour.
a) Define only a file - and it is searched everywhere in support paths
b) define it with full path - it is only searched there and nowhere else

Unfortunate for me you didn't see it sooner to save me the time

[Peter2]

...
a) Define only a file - and it is searched everywhere in support paths
...

If you mess up your files in your support paths and you have files with same name in different support folders - no matter if they are fonts or programs or something else - you have to check which file is really loaded.
I know the problem that you are checking and modifying and replacing your file in folder A, but Autocad uses the similar file from folder B..

[BIGAL]

The general rule for support files is start looking at top and once found stop but I only ever had 1 copy of custom menus, yes variations but different names. there is a up down in the support path use it push the user paths to top.

[tombu]

Tested it. For anyone in the future who is interested in this it turns out the CUI does somehow store the full path of the files. Moving lisps stored in the CUI this way, even if to a support path, causes them to not load.

As putting code into folders both in Support and Trusted Folders is simpler, more secure and easier to fix when network locations are modified I recommend you try this approach to avoid issues in the future. Have you looked into the TRUSTEDPATHS (System Variable)? http://help.autodesk.com/view/ACD/2021/ENU/?guid=GUID-2FB4611D-F141-48D5-9B6E-460EB59351AF
Like Mike.Perry who sinc quoted I've never used Startup Suite either as it's a poor replacement for acad.lsp, acaddoc.lsp, acad.rx, or *.mnl files which can easily be copied to other PC's, verticals and Versions. Google search for "startup suite not loading" returns About 8,580,000 results, first Swamp one: https://www.theswamp.org/index.php?topic=41923.0
Many users have used Startup Suite without issues or at least without noticing any but why take a chance?