RE: Dgnlib modification

Marc Thomas — Thu, 22 Jun 2017 15:54:36 GMT

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!

RE: Dgnlib modification

Bruce Reeves SRNS — Wed, 21 Jun 2017 15:39:53 GMT

We generally just make a "local copy" of the .dgnlib (somewhere NOT in the search paths of the applications), open it, edit it, and then replace it back where it came from (and same a copy of the original). To copy back, you'll have to wait until nobody is using the applications (so the file(s) are not locked).