From changeset 864 on, CHDK includes the ability to call Canon Event Procedures and arbitrary machine code functions. Together these are referred to as "native" calls. As of CHDK 1.2, native function calls may be enabled in the miscellaneous menu. Because there are event procedures and other functions which could permanently damage the camera (for example, by erasing the Canon firmware) this feature is disabled by default and cannot be enabled with set_config_value. If you use a third party script which requires this interface, it is your responsibility to verify that it is safe. If a script attempts to use native call functions when they are not enabled, a Lua error will be triggered. You can check whether native calls are enabled from script using get_config_value.
| Attributes | Values |
|---|
| rdfs:label
| - Lua/Lua Reference/Native Function Calls
|
| rdfs:comment
| - From changeset 864 on, CHDK includes the ability to call Canon Event Procedures and arbitrary machine code functions. Together these are referred to as "native" calls. As of CHDK 1.2, native function calls may be enabled in the miscellaneous menu. Because there are event procedures and other functions which could permanently damage the camera (for example, by erasing the Canon firmware) this feature is disabled by default and cannot be enabled with set_config_value. If you use a third party script which requires this interface, it is your responsibility to verify that it is safe. If a script attempts to use native call functions when they are not enabled, a Lua error will be triggered. You can check whether native calls are enabled from script using get_config_value.
|
| dcterms:subject
| |
| abstract
| - From changeset 864 on, CHDK includes the ability to call Canon Event Procedures and arbitrary machine code functions. Together these are referred to as "native" calls. As of CHDK 1.2, native function calls may be enabled in the miscellaneous menu. Because there are event procedures and other functions which could permanently damage the camera (for example, by erasing the Canon firmware) this feature is disabled by default and cannot be enabled with set_config_value. If you use a third party script which requires this interface, it is your responsibility to verify that it is safe. If a script attempts to use native call functions when they are not enabled, a Lua error will be triggered. You can check whether native calls are enabled from script using get_config_value. For applications where enabling native calls in the menu is not practical, you can build CHDK with OPT_FORCE_LUA_CALL_NATIVE=1 set in buildconf.inc Prior to release 1.2, native calls were only available as a compile time option. This feature is only available in Lua, not ubasic. The test script tstcallf.lua can be used to test this functionality, and also serves as an example.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)