Handles: Difference between revisions
No edit summary |
Replaced link to API |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
An object handle is used to reference a more complicated piece of data (such as a file, Flowcode component or block of text) whose internal format is not known. Flowcode provides many [[Simulation_Functionality|simulation macros]] that use handles to easily pass data around. | |||
An object handle is used to reference a more complicated piece of data (such as a file, Flowcode component or block of text) whose internal format is not known. Flowcode provides many [[ | |||
| Line 10: | Line 8: | ||
The handle [[Variable_Types|variable type]] can be used with the tree [[ | The handle [[Variable_Types|variable type]] can be used with the tree [[Simulation_Functionality|simulation macros]] to allow things like stepping through the [[Component_Tree|component tree]]. | ||
Latest revision as of 14:39, 23 July 2026
An object handle is used to reference a more complicated piece of data (such as a file, Flowcode component or block of text) whose internal format is not known. Flowcode provides many simulation macros that use handles to easily pass data around.
In an embedded context, a handle can be thought of as a pointer to memory, except Flowcode manages the handles so referencing a non-existent handle will not cause any fatal errors.
A handle value of zero is considered null and invalid to Flowcode.
The handle variable type can be used with the tree simulation macros to allow things like stepping through the component tree.