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. 

  • Unknown said:

    dgn libs are awesome and easy to find

    you just have to be clever  what you name them and where you put them then  make sure the work space config knows where they are

    That's what we would like to believe, and so it should be.

    But where is it explained in any way that's designed to be effectively communicative, rather than some geeky circular-referential illiteracy, which you can see is kinda pedantically true only after you already understand it?

    How did you come to understand all this? not from any publicly available documentation, I bet, but incrementally from your existing long experience in the Bentley walled garden and/or from long computer-immersion generally.

    Bentley keeps introducing things but never bothers to explain them, confident that their only 'audience' that matters is old-hand individuals and corporates' IT departments.

  • Thomas I have to disagree dgn libs are awesome and easy to find

    you just have to be clever  what you name them and where you put them then  make sure the work space config knows where they are ...

    eg  for levels

    We have drive\xxx\mstn\stds\levels

    in that we have

    Archi.dgnlib

    Survey.dgnlib

    Services.dgnlib etc

    under the standards folder I also have another folder for text and dim styles dgnlibs.

    Another for tool bars custom for differenet disciplines I have different interface.dgnlibs applied when you use specific work spaces...

    So Mr's Bentley dont go changing dgnlibs now they are awsome once you learn how they work..

    BTw you can even make a macro or F key to load specific dgn libs...

    but for levels I use the level manger import/attach  levels and choose the dgnlib of choice for the discipline name needed....

    Lorys

    Started msnt work 1990 - Retired  Nov 2022 ( oh boy am I old )

    But was long time user V8iss10 (8.11.09.919) dabbler CE  update 16 (10.16.00.80) 

    MicroStation user since 1990 Melbourne Australia.
    click link to PM me 

  • Unknown said:
    Well to be quite frank there are over 200 ideas in the ideas section and we have seen no indication that any of them have even been reviewed, let alone considered.   You guys want feed back from users but we are getting little feed back about the ideas we post.  Personally I'm starting to feel like it was a waste of my time writing them up.

    David,

    We listen and we review the ideas weekly if not more often.  If you notice one has been marked complete.  Currently there isn't a way to mark an Idea to anything other than Under review, Approved, or Complete and this is one of the reasons it is in the EAP section as this is also in a beta try process.  We have a process which is be set up which will move an item into development from the Ideas section but again this is in development.  We also have a criteria with which an item will be moved on but again this is a developing process.  Once we have the process refined we will move Ideas out into the public communities.

    Thanks,

    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

  • Tim,

    You can't tell from the standard pick lists where they come from.  Internal, external, rsc.  Theres no way to tell.

    Theres also no way to filter.  Only levels from this file.  Only Styles from this file.  Things start creeping in from all over and it takes an inordinate amount of time to sort it out.