Branded DGNLIB's: Yes?, No?, Does it matter?

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?

Parents
  • This is a great question.  We are using OpenRoads Designer and Bentley themselves have multiple dgnlibs in their workspace that need resources from other dgnlibs to function.  i.e., Graphical Filters , display style rules, feature definitions, and element templates that use linestyles, textstyles and dimstyles.  The only way to edited these libraries is the have a workset associated with the file.  What do we do?  Also , as these dgnlibs get copied into Projectwise the workset data will go with them.  From what I have read this screws up your managed workspace in Projectwise.  Bentley, Please give us some direction.

    Thanks

Reply
  • This is a great question.  We are using OpenRoads Designer and Bentley themselves have multiple dgnlibs in their workspace that need resources from other dgnlibs to function.  i.e., Graphical Filters , display style rules, feature definitions, and element templates that use linestyles, textstyles and dimstyles.  The only way to edited these libraries is the have a workset associated with the file.  What do we do?  Also , as these dgnlibs get copied into Projectwise the workset data will go with them.  From what I have read this screws up your managed workspace in Projectwise.  Bentley, Please give us some direction.

    Thanks

Children