comfilehmi:hmieditor_function:index
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
comfilehmi:hmieditor_function:index [2024/03/13 16:44] COMFILE Technology [System Functions] |
comfilehmi:hmieditor_function:index [2024/03/13 17:05] (current) COMFILE Technology [System Functions] |
||
|---|---|---|---|
| Line 174: | Line 174: | ||
| * ''tick_count()'' : The number of milliseconds since the system was powered on. This is a 32-bit millisecond timer that will overflow every 49.7 days. | * ''tick_count()'' : The number of milliseconds since the system was powered on. This is a 32-bit millisecond timer that will overflow every 49.7 days. | ||
| * ''touch_duration()'' : The number of milliseconds since the last time the screen was touched. If the screen has never been touched -1 is returned. | * ''touch_duration()'' : The number of milliseconds since the last time the screen was touched. If the screen has never been touched -1 is returned. | ||
| - | * ''verify_developer_key(value)'' : Using the ComfileHMI panel PC's runtime configuration screen, a unique key can be assigned to a individual device or group of devices. ''verify_developer_key'' can then be used at runtime within a project to test which device a project is running on and dynamically offer a different experience. The developer key cannot be read; one can only check if ''value'' matches the developer key assigned to the device. This function returns ''1'' if the ''value'' matches the developer key assigned to the device or ''0'' if it does not. This feature is only supported on PCs with a software licensing USB dongle. Whether or not this function is supported in the simulator is determined by runtime settings. The PC runtime verifies the given value against the developer key registered to the USB licensing dongle. | + | * ''verify_developer_key(value)'' : Using the ComfileHMI panel PC's runtime configuration screen, a unique key can be assigned to a individual device or group of devices. ''verify_developer_key'' can then be used at runtime within a project to test which device a project is running on and dynamically offer a different experience. The developer key cannot be read; one can only check if ''value'' matches the developer key assigned to the device. This function returns ''1'' if the ''value'' matches the developer key assigned to the device or ''0'' if it does not. This feature is only supported on PCs with a software licensing USB dongle. Whether or not this function is supported in the simulator is determined by runtime settings. The PC runtime verifies the given value against the developer key registered to the USB licensing dongle. The developer key can be registered to the USB licensing dongle from within the simulator or PC runtime settings. |
| | | ||
| ===== Action Parameters and Related Functions ===== | ===== Action Parameters and Related Functions ===== | ||
comfilehmi/hmieditor_function/index.1710315850.txt.gz · Last modified: 2024/03/13 16:44 by COMFILE Technology