TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: HasanCAD on April 28, 2016, 07:02:26 AM
-
in case of adding a lisp to *.cuix file and add another one on startup using applaod,
which one is start first?
-
Hasan,
Lengthy article by Steve Jonhson here: http://www.blog.cadnauseam.com/2008/09/01/what-is-loaded-at-autocad-startup-and-when/ (http://www.blog.cadnauseam.com/2008/09/01/what-is-loaded-at-autocad-startup-and-when/)
Here quoted from that article:
A. CUI files loaded:
1. Enterprise
2. Main
3. Partials to Main
4. Partials to Enterprise
B. acad*.* files loaded:
1. Files listed in acad.rx
2. acad2009.lsp
3. acad.lsp
4. acad2009doc.lsp
5. acaddoc.lsp
6. acad.dvb
C. CUI-associated MNL and LSP files loaded:
1. Enterprise named MNL
2. Enterprise loaded LSP and MNL
3. Main named MNL
4. Main loaded LSP and MNL
5. Partials to Main named MNLs
6. Partials to Main loaded LSPs and MNLs
7. Partials to Enterprise named MNLs
8. Partials to Enterprise loaded LSPs and MNLs
D. Startup suite files loaded
E. Startup routines run:
1. AcadStartup() called (AutoCAD startup)
2. AcadDocument_Activate() called (Drawing startup)
3. (S::STARTUP) called
-
Try it and see. Create a small lisp with only this line (alert "this is the file loaded with xxxx") for each case, replacing "xxxx" with the actual location.
In my test (AutoCAD 2016), the CUI loaded on loads first, then the APPLOAD one.
-
Hasan,
Lengthy article by Steve Jonhson here: http://www.blog.cadnauseam.com/2008/09/01/what-is-loaded-at-autocad-startup-and-when/ (http://www.blog.cadnauseam.com/2008/09/01/what-is-loaded-at-autocad-startup-and-when/)
Thanks ymg i'll use this sequence
-
Try it and see. Create a small lisp with only this line (alert "this is the file loaded with xxxx") for each case, replacing "xxxx" with the actual location.
In my test (AutoCAD 2016), the CUI loaded on loads first, then the APPLOAD one.
Good Idea i'll give this a try
-
After testing I figured out the cui lisp loaded first.
What I am doing is
I created a menu this menu saved on server. for any case if the server is off or no network ...etc. AutoCAd ca not load the *.CUIX file
so I am coping the *.CUIX file and lisps on C:\.
But I am facing a problem, copying lisp can not copy *.CUIX file because it is opened ready by AutoCAD.
Is there any solution?
-
I'd say back up the thought process a couple of steps. If users cannot access the server with the LISP/CUIx/etc., could they still access drawing files? How about network licenses? Or other work-related materials? If the answer is "no" then having a local-version of any support files won't help much.
-
I'd say back up the thought process a couple of steps. If users cannot access the server with the LISP/CUIx/etc., could they still access drawing files? How about network licenses? Or other work-related materials? If the answer is "no" then having a local-version of any support files won't help much.
Yes you are right, While the server is down there is no access for files, but I noticed that if the menu one server and not loaded because server is down, the next time I have to load the menu manually.
What I am doing is copy the menu then load from C:\
Is what saying logic?
-
If I understand you correctly, you're saying that you are loading a menu file that resides on the network.
Then if a user launches AutoCAD and the network resource is not available (for whatever reason...), that the menu is not available.
Then if the user launches AutoCAD again, and the network resource IS available, the menu still does not load?
If this is correct so far, then what we do is to check to see if the menu is loaded using some autolisp code in "acad.lsp" and if not, it loads it.
-
... and turn off automatic workspace saving. That kind of CUIx-not-found event produces a change to the workspace so it saves the new configuration. Blammo - no more menu, Ribbon tabs, etc. since the workspace no longer references it. As far as AutoCAD is concerned everything is functioning as it should.
-
This has been a known issue for for quite some time (2009 or so). If you are prone to downtime, from what I can tell the best workaround is to download copies of the lisp/cuiX routinely from a central server and work from local copies. This can be done from Windows AD or another 3rd party sync tool.