Sounds good Shaun...thank you. At CH we have taken the delivered OPM dataset and made an enterprise dataset, thus when we receive updated installs of OPM we can merge in any new content as needed and not lose our customizations. Thus, I proceeded to update the OPmodeler.dgnlib accordingly. The complicated part was to provide project-level ability to customize where needed, and we can do that by wholeheartedly copying our enterprise dataset to a project location and adjust accordingly, or by simply re-pathing the MS_DGNLIBLIST variable to a project-specific location for the DGNLIB. Ideally though, it would be nice to cascade the DGNLIB, so if I make "OPmodeler_project.dgnlib" and create a Supports \ Model element template to set a different level name, then this one setting would prevail over the enterprise "OPmodeler.dgnlib". In OPPID, the delivered dataset has "PIDProjectSymbols.dgnlib", and then "PIDUserSymbols.dgnlib", and then you can also overwrite anything in the active DGN file. In OPM, it doesn't seem like this cascading effect is there as I couldn't overwrite anything defined in the "OPmodeler.dgnlib" within the active DGNLIB. Am I making any sense?? Hope so...
↧