PM 8.11.7.xx SELECTseries 1

Hello Jan,

janvagner:

1) xfm metadata - text symbology: It seems to be, that since 8.11.07.xx the text-height and text-width symbology properties expect the master units values. In the 8.11.05.xx it expected the sub-unit values. Should we change our metadata (ie divide values by 1000) .... or is it a mistake on Bentley side? Or are there any settings (like use master units/ use sub units)?

In 8.11.07.xx TR 239617 was fixed to read text Height & Width from Xml metadata as master units values. Please update your metadata accordingly. Also verify that any LineSpacing, BackgroundBorderOffsetX, BackgroundBorderOffsetY values are also in master units.

janvagner:

2) xfm metadata - text symbology: now we have to set the new symbolgy value true for automatically applying text scale after editing feature. But for cell features we can use the UCF variable MS_GEOXFM_APPLY_SCALE_ON_EDIT = 1 instead. Why this variable doesn't work for text features too? Or is there any similar UCF variable for text features?

There is no similar variable for text features. The default text edit processing uses the text size/scale in the feature definition's symbology and ignores the current text geometry text size. If the ApplyScaleOnEdit symbology item does not exist in the feature definition, then default behavior of using text size/scale in the feature definition's symbology is used. If the ApplyScaleOnEdit symbology item exists, it must be set appropriately for your desired behavior. My guess is that you have ApplyScaleOnEdit symbology item in your Text symbology and that its value is OFF. If this is the case, then this symbology item will override the default behavior.

Regards,
Chris

Chris,

thanks for your quick response,  this mean that we MUST change our XFM project metadata. I am afraid that our customers use PM 8.11.5 as well as 8.11.7, in that case we will have to maintain two versinos of XFM metadata. That is not very convenient. Any suggestions?

thanks a lot Jan

Chris,

thanks for your quick response,  this mean that we MUST change our XFM project metadata. I am afraid that our customers use PM 8.11.5 as well as 8.11.7, in that case we will have to maintain two versinos of XFM metadata. That is not very convenient. Any suggestions?

thanks a lot Jan

Jan,

Here are a couple of possiblities:

1) Use text styles to define your text sizes

2) Create a custom criteria function to check software versions. Publish the function with mdlCExpression_publishFunction. You can check fcb->version for the Map version.

Regards, 

Chris

chris thanks for suggestions, please tell me, is there any other metadata change in the 8.11.7 like text symbology? thanks Jan

Hello Jan, 

In 8.11.7, we have added the "Display Name" item to the property definition.  In the feature definition, the text item previously labeled "Label" in Geospatial Administrator is now named "Display Name"(but the underlying Xml attribute name "alias" remained the same.....this same Xml attribute name is used for the new property definition display name).  In Map and PM, we are now using these values throughout the user interface.

Regards,

Chris

ok, thank you for info. jan