This is simply not necessary, and takes additional time at session start to load them ( regardless of one's computer hardware configuration performance). Instead, one is relegated to using your Ribbon the way FDOT ( you) have poorly chosen to implement it.įurther, Aecc*FloridaDOT registered applications have been added to the core product in lieu of being loaded only as part of an FDOT plug-in project, which means these applications are being loaded into each-and-every-session no matter if one is working on an FDOT project, or a California private client project. NET plug-in ( which is/was inefficient, had typo(s) in it, etc.), rather than CUIx, which precludes one's ability to save role-specific Ribbon components ( i.e., technician, designer, etc.) to one's own workspace. Which in and of itself is ironic, given that you implement the FDOT Ribbon via. ARG), which loads myriad registry changes, and saves to the 'Civil 3D' workspace ( stored in main CUIx, and applies to all Profiles), rather than creating a workspace of your own ( stored in your own CUIx). ( FDOT CADD Applications Developer):Ĭonsider the FDOT Profile (. But you knew that already, didn't you? LoL You can download the most recent release here ( issued ): please take from these comments what is applicable only. Should any of the concerns to follow be already corrected, improved, etc. I have not tested another release since then for reasons not discussed here. All 14 pages of comments, code snippets, and screenshots, specifically regarding session start, workspace, and registry - not even beginning to touch the actual plans production process ( using your tools), or tax payer funded Sheet Set Organizer application. With a little bit of AutoLISP knowledge and the instructions here, you can make this fix too.Firstly, the most recent release comments I provided FDOT was back in January 2013. McSwain: This is a very nice solution to a Xlist command limitation that could prevent a long layer name from displaying correctly. (/= (vl-file-size oldxlist) (vl-file-size newxlist)) (setq newxlist (findfile "serverPathLocationxlist.lsp")) You also can use acaddoc.lsp over a network to update the xlist.lsp file by adding this code in it. If you have AutoLISP knoledge, you can use this function to show more information about the selected entities such as handle, elevation, coordinate points, etc. Additionally, it won't search for any DCL file. (if (/= sLineType "")(setq line6 (strcat "Linetype: " sLineType " ")))īy using an alert box instead of a DCL file, it prevents AutoCAD from hiding some important information with long layer names. (if (/= sColor "")(setq line5 (strcat "Color: " sColor " "))) (if (/= sLayer "")(setq line4 (strcat "Layer: " sLayer " "))) (if (/= sObjectType "")(setq line3 (strcat "Object: " sObjectType " "))) (if (/= sStyleName "")(setq line2 (strcat "Text Style: " sStyleName " "))(setq line2 "")) (if (/= sBlockname "")(setq line1 (strcat "Block Name: " sBlockname " "))(setq line1 "")) (setq sAcadPath (substr sAcad 1 (- (strlen sAcad) 8))) (defun DisplayDialog ( / sAcad sAcadPath line1 line2 line3 line4 line5 line6 ) OR paste the replacement DisplayDialog function shown below, AFTER the one currently in the file Put the entire DisplayDialog function in comment by putting a semicolon ( ) character on each line. Open the file via the LISP editor (Vlide command) or simply with Notepad. You can find it by using (findfile "xlist.lsp") at the Command line. The solution is to modify the XLIST.LSP file.
0 Comments
Leave a Reply. |