This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
comfilehmi:string_variable:index [2020/03/01 16:12] COMFILE Technology [Fonts] |
comfilehmi:string_variable:index [2024/02/01 13:30] (current) COMFILE Technology [Fonts] |
||
---|---|---|---|
Line 13: | Line 13: | ||
===== Fonts ===== | ===== Fonts ===== | ||
- | With other widgets, the text displayed is usually numeric. The ComfileHMI Editor software is smart enough to recognize this and caches each digit as a bitmap using the [[comfilehmi:hmieditor_font:index|specified font]] when the project is compiled. This makes displaying the numeric text very fast. | + | With other widgets, the text displayed is usually numeric. Comfile Studio is smart enough to recognize this and caches each digit as a bitmap using the [[comfilehmi:hmieditor_font:index|specified font]] when the project is compiled. This makes displaying the numeric text very fast. |
- | However, with the String Variable widget, the text can be anything and the ComfileHMI Editor cannot perform the same optimization. Therefore, it must load either a built-in font, or a font file from the SD card's //Fonts// folder, and draw the text dynamically. Any font other than the built-in fonts must be manually copied to the SD card's //Fonts// folder in advance. | + | However, with the String Variable widget, the text can be anything and Comfile Studio cannot perform the same optimization. Therefore, it must load either a built-in font, or a font file from the SD card's //Fonts// folder, and draw the text dynamically. Any font other than the built-in fonts must be manually copied to the SD card's //Fonts// folder in advance. |
{{ :comfilehmi:string_variable:string_variable_font.png |}} | {{ :comfilehmi:string_variable:string_variable_font.png |}} |