S::Startup in ver8
Does version 8 support the S::Startup function to automatically fire up a given lisp file when Bricscad starts? It worked great upto version 7.I tried loading this in each of the "on_start", "on_doc_load" files, to no avail. The "autoload" function works the same as the (load "lispfilename"), in that it loads the lisp file, but it doesn't automatically execute it.Any help is appreciated.
Comments
-
I had trouble with autoloading until Tech Support told me to move my "On_start.lsp" file to the USER Support folder (that's the Support folder in C:/Documents and Settings/blah/blah/blah/....., not the one in C:/Program Files/BricsSys). I keep a shortcut to that folder in my Windows Start menu.I just have a (load "filename.lsp") in it for any lisp file I want loaded automatically, and it works pretty well. Or I guess you could put all your lisp routines into "On_start.lsp".They also told me about the cryptically named ACADLSPASDOC variable. If you set it to ON, or 1, then the lisp file is autoloaded every time you open a new drawing file, which I find helps.
0 -
Something that I've been wondering about:What is the difference between putting a command in "on_doc_load.lsp" inside"(defun s::startup () ...)" for example :"(setvar "CMDECHO" 0)" or "(load "mylisp")"or simply putting the command in "on_doc_load.lsp" without s::startup?
0 -
A wish. That the appload dialog had some check boxes, Load@start, LoadEachDoc, next to any lisp, .dll or such files you like. Seems like most of the house keeping already exist for such a feature. At any rate it would make modifications to startups so easy. Not sure I expressed my idea well, but just a wish anyway.Jerry
0 -
Yaacov -Yes, making direct lisp calls within the startup lisp can be helpful, where it serves a purpose.In my case, I have a Visual Basic front-end, where all the selections and decision making is performed. The VB app then switches to Bricscad and, with the s::startup feature, loads and executes the related lisp program, which essentially generates the intended drawing with the user selections.Alternatively, in the absence of the s::startup feature, I could simply build up a script file, and then call it as a startup parameter when loading Bricscad. But I would still prefer s::startup, since I can have some logic in the lisp file, while none in the .scr file.
0