Hi Owen,
I’ve just been experimenting with using your LspLoad for deployment (inconjunction with Inno setup). It works absolutely beautifully, except for the ”.13.brx” module is failing to load in Bricscad v13.1.6. (Windows 7 32bit).
I've rebuilt and updated the LspLoad.zip file; it should work now in V13.
That's done the job. Many thanks.
Hi Owen,
Are you able to give me an approximate indication of when BricsCAD V14 will be supported?
Many thanks
I should have time to work on it this afternoon, so look for an update later today.
Awesome. Thanks Owen!
Hi Owen,
Are you able to give an approx indication for when Lspload will support BricsCAD V17?
Many thanks (as ever!)
I just started today working on updating my own software. I'll try to get LspLoad updated today yet.
Just downloaded. Thank you!!! :)
Hi Owen,
Thanks again for this, it works, however starting with BricsCAD V17 (17.1.04 x64) - the following output is appearing on the command line at start up:
: (LspLoad-MyAppLoad)nil
: (vl-load-all "c:/Program Files/MyApp/Loader/MyAppLoad")(princ)
in BricsCAD Torsten includet an special Funktion some Jears ago. Its called vl-list-loaded-lisp. It determines where an loaded Funktion is stored. In coupple with the file on_doc_load.lsp you can create your own autoloader for Lisp or des Files.
And new in V17 is the demand-load functionality which was bevore only for *.brx and *.dll - now also usable for Lisp and des Files.
Hi CADwiesel,
That is most interesting, thank you very much indeed for your post.
Bricsys deliver again! :)
Thank you very much for the application, Owen. It is very useful. Just one question: is it possible that the digital signature data does not appear?
Quote from: diogenes on November 16, 2016, 06:47:52 AM
is it possible that the digital signature data does not appear?
Sorry, I don't understand the question. Can you rephrase please?
Hi, Owen. I've done the steps explained in the MyLispPlugin application. In Autocad 2016 and secureload = 1, when I start Autocad, it asks for confirmation to load MyLispPlugin and the following image appears:
(http://captura.png)
Could this message not appear?
Thank you for your work and greetings
Hi diogenes,
For AutoCAD 2014 through to AutoCAD 2016, you would have to either install lsploader into a "Trusted Path" or alternatively create a lsploader.bundle in Autodesk's Applications Plugins folder. See http://adndevblog.typepad.com/autocad/2013/01/autodesk-autoloader-white-paper.html.
Happily as from AutoCAD 2017, the Program Files folder tree is added to the Trusted Paths as a matter of course.
Again, thank you very much Owen
Quote from: diogenes on November 18, 2016, 12:55:28 AM
Could this message not appear?
The message is designed to give the end user an ability to block unauthorized code from executing. As already mentioned, there are ways your installer can configure the system so that the application code is trusted, but security is usually best left to Autodesk and the end user.
Thanks Owen.
I read in the material of Autodesk what you comment and it is totally logical, although for some users it is complex everything that is not to "plug and play", ;D ;D ;D
regards
I would say that this is not a problem of the signature, it is a result of your settings of "trusted paths" inside AutoCAD. If it is set "right" there will be no such message - neither for signed nor for unsigned files.
This message will always prompted, if an not registered Application wants to be loaded. You can change this eveb if you set secureload to 0 or set this application on the list of trusted files. See sysvar TRUSTEDPATHS
Hi Owen,
Any chance of adding support for BricsCAD V22 to your lovely LspLoader?
With much thanks
Dan
LspLoad has been updated with BricsCAD V22 support.
Hi Owen, much appreciated. Thank you :)