dp_fct_expressions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dp_fct_expressions [2023/04/19 18:38] – toddmalone | dp_fct_expressions [2023/04/19 18:52] (current) – toddmalone | ||
|---|---|---|---|
| Line 29: | Line 29: | ||
| </ | </ | ||
| + | |||
| + | Another feature of the dp_fct is to call a library function. | ||
| + | |||
| + | To use a function, you will still need to setup the p1, p2, etc. as these become the library variables passed into the function. | ||
| + | |||
| + | The trick to all this is to setup the system to recognize your functions in the library. | ||
| + | < | ||
| + | [event] | ||
| + | loadCtrlLibs = " | ||
| + | </ | ||
| + | |||
| + | A function might look like this: | ||
| + | < | ||
| + | float tableLookup(anytype p1, anytype p2) | ||
| + | { | ||
| + | float fRet; | ||
| + | // table lookup with arrays, mapping, etc. where fRet = something | ||
| + | return(fRet); | ||
| + | } | ||
| + | </ | ||
dp_fct_expressions.1681929489.txt.gz · Last modified: by toddmalone
