Level libraries in csv or xls instead of dgnlib

Unknown said:

I don't like dgnlibs because it is not obvious what is stored in which dgnlib.

That depends on your configuration. AFAIK we aren't limited to the number of DGNLIBS we can use so a good practice that I employ is to keep 1 dgnlib for 1 configuration item alone and not pile multiple settings into 1 dgnlib so I end up with something like:

• levels.dgnlib
• text_styles.dgnlib
• dimensions.dgnlib
• print_styles.dgnlib
• tasks.dgnlib
• menus.dgnlib
• display_modes.dgnlib

Hi Barry,

Though this works for some items and in some cases it does not work for anything that has a dependency on another item.  For instance a Dimension style may use a text style.  Once this occurs you have a copy of your text style in the Dimension style DGNlib. If you make a change to what is believed to be your source of truth (text_styles.dgnlib) it wont be seen by your dgns as when we process the variable MS_DGNliblist we take the first instance of the text style we find and that would come from the file dimensions.dgnlib.

Now the first thing people will say and has been said in this thread is to just make a variable for each of the types of thing to be found, for instance MS_DGNliblist_TextStyle.  Well that doesn't work either.  Take the scenario above.  If you use the dimension style before the text style then the text style from the dimension style file is brought into the active dgn.  Thus you are using the wrong definition.

The best solution is to have things that are cross dependent placed in one file.  In your case the first 3 things should be in one file.  I go as far as to say that MS_DGNLibList should include the the variables MS_CELLLiblist and MS_Seedfiles.  This way your management dialogs get a true picture of all the content that is out there that may be appearing in your files.

HTH,

John

Hi Barry,

Though this works for some items and in some cases it does not work for anything that has a dependency on another item.  For instance a Dimension style may use a text style.  Once this occurs you have a copy of your text style in the Dimension style DGNlib. If you make a change to what is believed to be your source of truth (text_styles.dgnlib) it wont be seen by your dgns as when we process the variable MS_DGNliblist we take the first instance of the text style we find and that would come from the file dimensions.dgnlib.

Now the first thing people will say and has been said in this thread is to just make a variable for each of the types of thing to be found, for instance MS_DGNliblist_TextStyle.  Well that doesn't work either.  Take the scenario above.  If you use the dimension style before the text style then the text style from the dimension style file is brought into the active dgn.  Thus you are using the wrong definition.

The best solution is to have things that are cross dependent placed in one file.  In your case the first 3 things should be in one file.  I go as far as to say that MS_DGNLibList should include the the variables MS_CELLLiblist and MS_Seedfiles.  This way your management dialogs get a true picture of all the content that is out there that may be appearing in your files.

HTH,

John