Level libraries in csv or xls instead of dgnlib

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

Now we have level libraries in dgnlibs. Which is  the active file looks in another file for the data.

So why can't we have the active file look in something more transparent and readable than a dgn? Like a csv, or a xls, which can be viewed parallel to the active dgn in ustn.

It would also be much easier to edit than through LM in ustn. 

Parents
  • 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
    Its pretty much a fool-proof setup and if there is ever any glitch at least I can pin-point while file to investigate, plus it also means I don't have to have MS_DGNLIBLIST and MS_GUIDGNLIBLIST sharing the same values.
  • Barry

    in perfect world and if you remember exactly what you thought two years ago and never did anything wrong that might be a system.

    But i have many more things to think of than where I stored some task two years ago. So at each point in time when I need this information I should be able to find out by the UI.

    Text and dimstyles you can, if you happen to find out. But not levels.and other things.

    regards / Thomas Voghera

Reply Children
No Data