Issue 31093 — DOC: entity/area-frames extensions compatibility implications not documented
Status: Solved in 10.2.01
Solution available in patch(es): G101
Summary: Uniface: The compatibility implications of the new entity/area-frames extensions that were introduced in Uniface 9.7.01 are not documented. Environment: +Uniface: Version 9.7.01 +Operating System: OS independent +Database: DBMS independent Symptoms: The compatibility implications of the new entity/area-frames extensions that were introduced in Uniface 9.7.01 are not documented. Area frames and the default entity widget have been significantly enhanced with new styling properties. These enable you to apply a flat border and set its color, shade the background in different colors, and apply a colored drop shadow. Compatibility: * Properties defined in the usys.ini take a lower precedence than the properties defined in IDF or set with 4GL functions. - $entityproperties overwrites the properties defined in the usys.ini. - Colors defined in the GFP popup menu take precedence over the property string in the usys.ini. - Properties defined in the usys.ini can only be used when the defined entity does not have properties set. * When a border is defined in the GFP it will always appear. There is no way to switch it off as an application modernization option. Colors, gradient and even the new Groove and flat borders can be used on the existing frames but again no influence on the existing old border.
There is no known workaround for this problem.
There are compatibility issues when combining the new styling properties for area frames and entity frames with the existing Border and Color properties. If both the Border and BorderType properties are set, two borders are displayed. Only a flat BorderType can be styled. If Color is set, all properties set in the initialization file are ignored, including BorderType and colors.