CMS 8.0 LISP path spec item
Posted: Mon Dec 08, 2014 3:27 pm
I see there is now a LISP item in the Paths/Files tab on the configuration dialog.
For some reason it does not do what I expected, that is, add my specified LISP folder location to the Support Paths.
It seems to halfway work. I say halfway because I have an autoload.lsp routine that is embedded in icaddoc.lsp, which is designed to load specified LISP routines only when their command name is entered. (This is OLD ACAD methodology, and was working as expected in my CMS 7.2) The nice thing about this is the command isn't loaded unless needed, thereby saving system resources.
For example, I have a short routine that changes the last object in the drawing to another layer. I enter CLLAY and the autoload routine "sees" I've typed CLLAY, loads CLLAY.LSP if it wasn't used previously in the session, and invokes the command.
Now this does not work, but if I do (load "CLLAY") the system has no trouble finding the routine. The flaw could be in my autoload.lsp code, but it is unchanged from what I used under CMS 7.2, so that tells me something's amiss... but what?
For some reason it does not do what I expected, that is, add my specified LISP folder location to the Support Paths.
It seems to halfway work. I say halfway because I have an autoload.lsp routine that is embedded in icaddoc.lsp, which is designed to load specified LISP routines only when their command name is entered. (This is OLD ACAD methodology, and was working as expected in my CMS 7.2) The nice thing about this is the command isn't loaded unless needed, thereby saving system resources.
For example, I have a short routine that changes the last object in the drawing to another layer. I enter CLLAY and the autoload routine "sees" I've typed CLLAY, loads CLLAY.LSP if it wasn't used previously in the session, and invokes the command.
Now this does not work, but if I do (load "CLLAY") the system has no trouble finding the routine. The flaw could be in my autoload.lsp code, but it is unchanged from what I used under CMS 7.2, so that tells me something's amiss... but what?