Load Application Files needs to be fixed

As a plug-in developer I have a serious problem with the Load Application Files dialog box, the one that pops up on the APPLOAD command.I need something like AutoCAD's startup suite. The end user needs to add the plug-in file just once and it will automatically load henceforth on startup. I know there are other mechanisms like adding LISP code to a startup LISP program or some .rx file containing the list of plug-ins to be loaded on startup. These are too confusing for customers.In fact, I would like to take this a step further and borrow an idea from other CAD systems. I develop plug-ins for other CAD systems as well and almost all of them have a system whereby a product installer can register the plug-in with the application so that the user does absolutely nothing apart from running an installer. They do this by using the good old Windows registry. On startup the CAD program looks for plug-in entries in a certain registry key and loads them on startup. So plug-in developers such as myself simply make our product installers add the necessary registry keys. Moreover these keys are automatically removed when the customer uninstalls the plug-in. So everything is kept tidy and organized.If someone at Bricsys needs additional information about such a mechanism I would be glad to provide it.Regards,Deelip Menezeswww.deelip.com

Comments

  • Hi Deelip,Thank you for your suggestion. In first stage, we should focus on the extension of the appload dialog, with the "startup suite" feature. Implementing other load mechanisms that are not supported in AutoCAD, does not seem feasible at this time. We have scheduled a task for the "startup suite" functionality. We estimate we can fit it into our development schedule in the course of Q1 2009.Best regards,Luc De Batselier

  • Thanks.Deelip Menezes

  • Implementing other load mechanisms that are not supported in AutoCAD <<<FYI AutoCAD does support autoload via the registry as Deelip mentions I.eDESCRIPTION (String): Insert the description of your arxLOADER (String): The full path and filename of your arx. For example: C:\Program files\MyApp\MyModule.arxLOADCTRLS (DWord) set its value to 0x0000002 (this value means "load on acad start")It is used for the more professional developers.

  • I would love to see a check box in the "APPLOAD" dialog that would commit these applications to "on_start",.. or remove them. ACAD or no, the object is the best CAD system.

  • HI, COULD ANYONE HELP OUT WIH THE FOLLOWING i.e. whats the syntax/structure/command for autoloading an arx application. Do we use the on_start.lsp file?>>> Implementing other load mechanisms that are not supported in AutoCAD <<< FYI AutoCAD does support autoload via the registry as Deelip mentions I.e DESCRIPTION (String): Insert the description of your arx LOADER (String): The full path and filename of your arx. For example: C:\Program files\MyApp\MyModule.arx LOADCTRLS (DWord) set its value to 0x0000002 (this value means "load on acad start") It is used for the more professional developers.

  • I'm a lisp programmer.... but Daniel Marcotte wrote a handy DRX application for document tabs.http://www.theswamp.org/index.php?topic=22658.0It is located via the "C:\Program Files\Bricsys\Bricscad V9\Support\autoload.rx" filemy autoload.rx file looks like this:----------------------------------;write comments hereDRXDocTabs_2.06_8.drx----------------------------------in this case the: DRXDocTabs_2.06_8.drx file is located in the "C:\Program Files\Bricsys\Bricscad V9\Support\" folder.By they way that program is really helpful! Thanks Dan if your reading this... Steve

  • Hello, everyone,since around 2...3 months, Bricscad also supports "DemandLoad" for *.arx/brx/drx/dlll (in fact, any file type - but file must be a valid arx/brx/drx file - meaning, a DLL base type).This DemandLoad works exactly as in Acad, and also inside Registry, the same keys are used - so it is extremely simple to adjust installer routines.Additionally, for BRX based applications, even the ARX-like API is present in BRX : AcadAppInfo, which can be used by arx/brx/drx applications to add those DemandLoad entries to Registry.Currently, those loading type flags are supported :0x1 : OnProxy -> this is currently implemented as 0x2 (OnStartup), until better callbacks from ODA kernel is provided0x2 : OnStartup -> the module file is loaded on every Bricscad startup0x4 : OnCommand -> when a defined command is enteredAs not yet documented in Bricscad & developer documentation, it is available in the same style and logic as in Acad / ARX.I hope this will help ?Many greetings to all.

This discussion has been closed.