Hi all,
I have recently adopted the procedure of placing several custom tool palettes on a network drive, and then switching the sysvar
*_TOOLPALETTEPATH to control which toolpalette my workstations are using.
This works great.
My trouble is when the user wants to go back to the stock Civil3D toolpalette. The palette groups are wiped out after changing toolpalette path. This is only a problem due to the extremely large amount of palettes that are shipped with Civil3D 2010. I've considered exporting the stock palettes into their own subdirectories, but I would have to do this again next year when 2011 is shipped.
Here's my findings: the profile.aws file does not get updated... until you exit Acad. So, in other words, the profile.aws file seems to be hunky-dory, and the toolpalette groups should function properly when the user switches the path back to the stock location. But, as soon as the user exits ACAD, the profile.aws file gets overwritten, and the grouping section is cleared out.
I do apologize for bringing this horse back to be beaten again, but there has to be a better way.
craig
Edited by: ctbailey on Jun 2, 2009 1:37 PM
_______
Craig T. Bailey, PE, LLS, PSM
Bailey Associates
www.bailey-associates.com