[CONNECT] Does it matter which dgnliblist variable is used to load named expressions?

Hi Kevin,

Any Named Expressions DGNLIBs included by MS_GUIDGNLIBLIST will be available to the whole application.

MS_DGNLIBLIST_PRINTING is intended to be used to keep separate content relevant to printing separate from other DGNLIBs reducing the chances of cross-contamination between DGNLIBs.

The only expressions that would be available to the Print dialogs would be those where the Print Set box is checked so storing these in a DGNLIB defined by MS_DGNLIBLIST_PRINTING would be best practice.

The pre-defined print expressions are hard coded and cannot be edited (Can you modify the pre-defined named expressions in Print Organizer?).

Hallo Marc & Kevin,

Just a comment. Previously you could include Named Expressions in any .dgnlib file in the MS_DGNLIBLIST variable to be globally available, but this is not true as of U16 it seems.

We have used Named Expressions to control visibility for Toolbar and Ribbon buttons in versions from V8i to CONNECT U14 and the Named Expressions contained in the dgnlib files in the MS_DGNLIBLIST variable was included and could be used everywhere. From CONNECT U16 (now 16.2) we had to move the definition of the Named Expressions to a dgnlib file that is referenced by the MS_GUIDGNLIBLIST variable as you stated above.

After the move everything worked again as it did previously. Just export a XML of the Named Expressions and Import them into the new DGNLIB. Then delete the old definitions from the old DGNLIB file.

Kind Regards,

Francois Grobler

Hi Francois,

I suspect if Named Expressions worked in the ribbon without being specified by MS_GUIDGNLIBLIST that was an inconsistency that we fixed. There has been some effort to provide granularity of DGNLIB control via variables specifying library purposes; i.e. MS_GUIDGNLIBLIST along with MS_DGNLIBLIST_TEXTSTYLES  etc.

"There has been some effort to provide granularity of DGNLIB control via variables specifying library purposes"

This is currently driving me crazy, especially with ORD built on older MicroStation platforms. I like the specific variables rather than the general MS_DGNLIBLIST but so far I found:

1. Can't put element template dgnlibs only in MS_DGNLIBLIST, must put them in MS_DGNLIBLIST_ELEMENTTEMPLATES. (even if MS_DGNLIBLIST_ELEMENTTEMPLATES is undefined)
2. Can't put dimension styles in MS_DGNLIBLIST_DIMENSIONSTYLES, must put them in MS_DGNLIBLIST. This may be specific to ORD 10.9 which is built on fairly old MicroStation. Haven't tested 10.10 yet (or latest MicroStation) yet.

P.S. I think everybody on this forum would put out a contract on me, but I would love MS_GUIDGNLIBLIST to be renamed to MS_DGNLIBLIST_GUI for consistancy. I believe the Color book libraries variable always points to dgnlibs so i'd be for renaming it as well.