Level libraries in csv or xls instead of dgnlib

Why can't there just be a really simple way to view in (optional, configurable level of) detail the contents of things like dgnlibs, seeds, even datasets? Doesn't have to be put into xml, csv or xls, just a configurable viewing tool, which can stay open as a window to refer to (or print out). Bit like ConfigExplorer. Incl what ways the seed (and dgnlib?) has been over-ruled in the current (or any selectable) dgn. Incl a bit of history, per item, of updating in either direction.

Hi Tom,

Unknown said:

Why can't there just be a really simple way to view in (optional, configurable level of) detail the contents of things like dgnlibs, seeds, even datasets? Doesn't have to be put into xml, csv or xls, just a configurable viewing tool, which can stay open as a window to refer to (or print out). Bit like ConfigExplorer. Incl what ways the seed (and dgnlib?) has been over-ruled in the current (or any selectable) dgn. Incl a bit of history, per item, of updating in either direction.

but there is export yours standard dgnlib file (... being stand means it should not change  without you knowing about it...) to CSV  and open with excel or print to a book  for desk reference..

or else just open the dgn lib itself read only with ustn ..

Lorys 

PS 

Have a look at Keith Little's book "survivors  guide  " see section  on levels and DGN libs thats how I learnt about dgnlibs...

Hi Tom,

Unknown said:

Why can't there just be a really simple way to view in (optional, configurable level of) detail the contents of things like dgnlibs, seeds, even datasets? Doesn't have to be put into xml, csv or xls, just a configurable viewing tool, which can stay open as a window to refer to (or print out). Bit like ConfigExplorer. Incl what ways the seed (and dgnlib?) has been over-ruled in the current (or any selectable) dgn. Incl a bit of history, per item, of updating in either direction.

but there is export yours standard dgnlib file (... being stand means it should not change  without you knowing about it...) to CSV  and open with excel or print to a book  for desk reference..

or else just open the dgn lib itself read only with ustn ..

Lorys 

PS 

Have a look at Keith Little's book "survivors  guide  " see section  on levels and DGN libs thats how I learnt about dgnlibs...

Unknown said:

Have a look at Keith Little's book "survivors  guide  " see section  on levels and DGN libs thats how I learnt about dgnlibs...

All,

There are quite a few suggestions in this thread.

May I suggest that you review the comments made here and add them to the Ideas section in the MicroStation EAP1 Forum that I know several (if not all of you) contribute to.

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.

Marc

Unfortunately I don't seem to make myself understood here.

See comment earlier in this thread.

I test case would perhaps be if I name my dgnlbs in Swedish - and you were tasked to understand what was stored in each dgnlib.

I am not sure I follow what is being asked here….

In an active file that has:

Levels from a DGNLIB

Textstyles from a DGNLIB

DimensionStyles from a DGNLIB

LineStyles

Etc,,,

These can all be found where they are coming from.

If the item is bold in the list , it is a local item

There is a column in level manager that tells you where the level exists

If you hover over some items, these state where they exist