Display name storage

Display names of components and slots are stored on the parent of a component or slot.

Explicitly-assigned display names are stored in the display “name map” of the parent component. This applies whether you manually assigned a display name, or used the Batch Editor for adding/editing display names.

displayNames slot

The “displayNames” slot on the parent component uses the data type baja:NameMap. This slot is created upon the first explicit display name given to a child slot. If the displayNames slot already exists, any new explicit display name is appended to its BNameMap value.

From the slot sheet of a parent, all child slots that have been explicitly-assigned a display name appear with a bold Display Name value.

Config flags

Often by default, the displayNames slot of a component has config flags set to “rho”, meaning it is read-only, hidden (from property sheet), and operator-level.

Figure 6.   Default config flags for displayNames slot of a component or container
Image

When using the Batch Editor to edit display names, you often need to change config flags on displayNames slots. You can do this either from slot sheets of components, or in a batch method via the Batch Editor.

NameMap value

After “unhiding” a displayNames slot from the slot sheet, you can see its NameMap value on the property sheet—or at least a portion of this value (the property field size is fixed, so typically some of the NameMap value is obscured).
Figure 7.   Example “Name Map” value of displayNames slot of parent with 3 entries
Image

In the preceding figure, the property sheet shows a portion of the NameMap value in the unhidden displayNames slot.

BNameMap syntax

The Baja NameMap value of the displayNames slot uses a “key=value” pair syntax, as follows:

{slotFirst=displayValue1;slotNext=displayValue2;slotLast=displayValue3;}

If manually-assigning display names, this syntax is unimportant—as it is always incorporated. However, if using the Batch Editor to edit or add displayNames slots, then you must follow this syntax exactly. Note even if only one child slot is assigned a display name, a semi-colon is required at the end of the value string. For example:

{slot=displayValue;}
{OA_Temp=Outside Temp;}

Note if the NameMap value contains multiple key-value pairs, it makes no difference in the order that they are listed.