• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 21 subscribers
  • Views 3030 views
  • Users 0 members are here

Dgnlib modification

Roland Cyr
Offline

I have gone thru and searched for the answer to this question on best practices to modify a dgnlib.

When modifying a dgnlib file is it best to:

Wait until after normal business hours when everyone is out Microstation to open and modify a dgnlib file?

Copy the dgnlib to either another named dgnlib file or should it be a dgn then, modify the dgnlib / dgn outside the normal workspace and restore it back to the previous dgnlib file name (when everyone is out of Microstation)?

I have read that to export the dgnlib file with levels to csv. Modify csv file and re-import csv into dgnlib. (so what about tool customization or templates?

Just trying to figure out best practice to modify a dgnlib file. My guess is to always open and modify a dgnlib file after hours when, nobody is using Microstation from the workspace that has the dgnlib configured.

 

Parents
  • 0

    It is best practice to manage dgnlib files outside the day to day working configuration. One method is by using an administrator User Configuration file containing appropriate variables.

    For instance I have one that I have used in the past called NoDGNLIB.ucf that contains the additional variables:

    MS_DGNLIBLIST = Setting this to null stops DGNLIBs loading so it is easier to see what is in the DGNLIB you are working in
    MS_GUIDGNLIBLIST > $(_USTN_USER)*.dgnlib This adds the admins _USTN_USER folder as configured location for UI DGNLIBs so you can play around without anyone else seeing the work in progress. MS_DGNLIBLIST = will need to be commented out (or just have another UCF) for UI customisations to be able to see site resourecs.
    _USTN_DISPLAYALLCFGVARS = 1 Shows systems variables as well as user variables. This can also be set as a Windows Environment Variable for admin users.
    The following two are needed if editing print configurations has been hidden/disabled
    MS_PLTFILE_EDITOR = MicroStation To override MS_PLTFILE_EDITOR = hide_menu_item
    MS_PLTDLG_ENABLE_SAVE_CONFIG = 1 If MS_PLTDLG_ENABLE_SAVE_CONFIG is set to '0', the plot dialog save configuration menu items are disabled.
    MS_VBA_OPEN_IN_MEMORY = NONE needed to allow editing of organisation VBA if it is set elsewhere in the configuration as MS_VBA_OPEN_IN_MEMORY = ALL

    Hope this is helpful!

    Marc

Reply
  • 0

    It is best practice to manage dgnlib files outside the day to day working configuration. One method is by using an administrator User Configuration file containing appropriate variables.

    For instance I have one that I have used in the past called NoDGNLIB.ucf that contains the additional variables:

    MS_DGNLIBLIST = Setting this to null stops DGNLIBs loading so it is easier to see what is in the DGNLIB you are working in
    MS_GUIDGNLIBLIST > $(_USTN_USER)*.dgnlib This adds the admins _USTN_USER folder as configured location for UI DGNLIBs so you can play around without anyone else seeing the work in progress. MS_DGNLIBLIST = will need to be commented out (or just have another UCF) for UI customisations to be able to see site resourecs.
    _USTN_DISPLAYALLCFGVARS = 1 Shows systems variables as well as user variables. This can also be set as a Windows Environment Variable for admin users.
    The following two are needed if editing print configurations has been hidden/disabled
    MS_PLTFILE_EDITOR = MicroStation To override MS_PLTFILE_EDITOR = hide_menu_item
    MS_PLTDLG_ENABLE_SAVE_CONFIG = 1 If MS_PLTDLG_ENABLE_SAVE_CONFIG is set to '0', the plot dialog save configuration menu items are disabled.
    MS_VBA_OPEN_IN_MEMORY = NONE needed to allow editing of organisation VBA if it is set elsewhere in the configuration as MS_VBA_OPEN_IN_MEMORY = ALL

    Hope this is helpful!

    Marc

Children
No Data
Communities
Support and Services
Training and Learning
Social Media