Version 15.2.05 on_start.lsp

even though I have this set to load with every drawing it does not seam to be working. I have lsp files that I have to load manually each time I open a file. any suggestions?

Comments

  • Try moving the contents of your on_start.lsp to a .mnl file of the same name as your .cui file.  I use a custom .cui file named enco_B15.cui which is located in c:\cadmaster.  My .mnl file is in the same directory and is named enco_B15.mnl.
  •  Or create an "on_doc_load.lsp" with your .lsp s.
  • ... Or change your ACADLSPASDOC setting.
  • I keep all my lisps in a directory of my own (C:\...Dwgs) and set Bcad to start in that directory.
    Then I don't have to go hunting for the latest place Bcad is looking for them.
  • I have an on_doc_load created which is triggered by my on_start.lsp and it does not work after updating, this same setup has been working fine since version 13.
  • Dear Rob,

    a) ACADLSPASDOC=1
    b) do not load "on_doc_load.lsp" from inside "on_start.lsp" ... "on_doc_load.lsp" is loaded automatically by BricsCAD, regardless of "on_start.lsp"

    Also, verify with
    (findfile "on_doc_load.lsp") if your intended file can be found

    Many greetings !
  • You do not say exactly what is not working.  I received a response to a bug report for V15.2.05 that said there is a timing issue that can prevent part of the lisp system from loading.  It was suggested that I add

    [code](if (not ai_dcl) (load "lispex.lsx"))[/code]

    I have this in my .mnl file, but it should work in on_start.lsp or on_doc_load.lsp.  This should only be needed until the next update is published. 

    FWIW, I changed from on_doc_load.lsp to a .mnl file at Torsten's suggestion.
  • have to admit I'm not exactly sure what a .mnl file is, my main problem is my LSP files are not loading. after removing the on_doc_load from my on_start I now have on LSPfiles loading but not the rest. let me ask this what should my on_start.lsp file contain and what should my on_doc_load file contain. I really only have 11 lsp files of which I probably on use 4 or 5 that need to load.

  • Put your lisp files in "on_doc_load.lsp"
  • Now the one file I had loading will not load now.

    on_start contents:

    ;this file will run once when the program starts.
    ;please do not edit. For custom actions on starting the program please create a file on_start.lsp.

    (command "vbaload" "c:/tos/tosvba_bcad.dvb")
    ;(command "-vbarun" "")

    on_doc_load contents:

    (load "Acettest.des")
    (princ)

    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/xplode.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/addlisp.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/ddptype.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/ddshapes.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/dlf.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/mvsetup.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/edge.lsp")
    (load "c:/Program Files (x86)/Bricsys/BricsCAD V15 en_US/support/ddvpoint.lsp")

    subsequently my Express Tools no longer works with this version... I know that's a third party add on but that may require me to go back a version.....

  • I got it working now..... after adding (if (not ai_dcl) (load "lispex.lsx")) to my on_start file everything is working as it was even the express tools..... thank for all your help.
  • Dear Rob,

    indedd, the ExpressTools support was affected by the actual timing bug - as result, the "AcetTest.des" did trigger
    a Lisp error, and as result of that, loading your on_doc_load.lsp stopped ...

    So, glad that it is also the same bug (with potential workaround, as Martin mentioned) - but sad about that bug at all :-(

    Fortunately, that workaround code could stay on the code - it will not conflict with the fixed version.
    Btw., our test system now also verifies proper loading of internal "lispex.lsx" file, to prevent such issue for the future.

    Many greeitngs to all !
  • Thanks for the workaround code!
  • This timing issue had been fixed in V15.2.06 ... fortunately, the workaround code does not conflict with the fixed timing.
This discussion has been closed.