Difference between revisions of "Handles"
From Flowcode Help
Jump to navigationJump to search (Created page with "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 provi...") |
|||
| Line 1: | Line 1: | ||
| + | <sidebar>Sidebar: Flowcode Help Overview:Variables</sidebar> | ||
| + | |||
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 [[API Overview|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 [[API Overview|simulation macros]] that use handles to easily pass data around. | ||
Latest revision as of 09:10, 17 May 2017
<sidebar>Sidebar: Flowcode Help Overview:Variables</sidebar>
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.
