Fonts optimization
The system automatically creates a necessary fonts subset, based on the really used characters on pages. This guarantee the target memory used optimization.Unfortunately, for some components, (e.g.: StringChooser) it’s not possible to know which characters are used because the string is composed at runtime with live values.For such components it’s possible to tell GF_Project to deploy a full UNICODE font, in place of an optimized one. Please note: this condition will require more memory and could also require to increase the target installed memory. Information about used memory is available in the SID tool, inside GF_Project.To do this, it’s necessary to know the font combination used (e.g.: SansSerif-12- Bold) and select it inside the font configuration tool, clicking over the button under the “deploy” column. The following screen will be shown:
Here it’s possible to select which font needs to be fully deployed.The components which this kind of approach should be useful are:StringChooserPanelAlarmDisplayPanelAlarmDisplayTouchPanelAlarmHistoryPanelDataHistory“Diagnostics” group components, if “I/O” description strings have been used.To easily find the critical components (e.g.: StringChooser) it’s advised to do a GF_Project global search (e.g.: search “stringchooser”).
Here it’s possible to select which font needs to be fully deployed.The components which this kind of approach should be useful are:StringChooserPanelAlarmDisplayPanelAlarmDisplayTouchPanelAlarmHistoryPanelDataHistory“Diagnostics” group components, if “I/O” description strings have been used.To easily find the critical components (e.g.: StringChooser) it’s advised to do a GF_Project global search (e.g.: search “stringchooser”).