842
edits
Using listeners and signals with Nasal: Difference between revisions
Jump to navigation
Jump to search
Using listeners and signals with Nasal (view source)
Revision as of 10:22, 15 July 2020
, 15 July 2020→setlistener(): OOP and setlistener
(→setlistener(): testing indicated that this is the way it works.) |
Legoboyvdlp (talk | contribs) (→setlistener(): OOP and setlistener) |
||
| Line 106: | Line 106: | ||
<syntaxhighlight lang="nasal"> | <syntaxhighlight lang="nasal"> | ||
myCallbackFunc([<changed_node> [, <listened_to_node> [, <operation> [, <is_child_event>]]]]) | myCallbackFunc([<changed_node> [, <listened_to_node> [, <operation> [, <is_child_event>]]]]) | ||
</syntaxhighlight> | |||
You cannot refer to OOP methods directly -- to do so, enclose the function call in a func() { } block as such: | |||
<syntaxhighlight lang="nasal"> | |||
signal.listener = setlistener(node, func() { me.phaseFunc(); }, 0, 0); | |||
</syntaxhighlight> | </syntaxhighlight> | ||