When opening .dgnlib files to edit levels, text styles, or whatever, I am often confronted with the WorkSet Alert dialog.
Since dgnlibs will be used by multiple WorkSets I usually like to have mine not branded - No WorkSet. Sometimes, however, I'll be in a hurry and just click the Open button on the alert dialog, and brand the dgnlib to my active WorkSet. So far I have not encountered any adverse effects of branding vs. not branding dgnlibs.
Is there anything good or bad about branding your dgnlibs, not branding your dgnlib to a WorkSpace, or doesn't make any difference?
There shouldnt be an issue with having the dgnlibs branded to a workspace/workset but ideally i would say it best to work in a no workspace/no workset environment so other dgnlib content gets loaded when working in the file.
i can file an enhancement to suppress the alert dialog if the file is a dgnlib is this would find that helpful.
David Trejo-Rodriguez said:i can file an enhancement to suppress the alert dialog if the file is a dgnlib is this would find that helpful.
That's the answer, but will Bentley actually do that? [a workaround]You could just close your file first, then select No Workspace. After you open a few libs they're show up on the MRU list.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley