ScriptInvoker Usage – Arma Reforger
Lou Montana (talk | contribs) (Page creation) |
(Fixed the error with templates) |
||
Line 74: | Line 74: | ||
The <enforce inline>ScriptInvoker</enforce> class used above is the "default" one used for methods without arguments. | The <enforce inline>ScriptInvoker</enforce> class used above is the "default" one used for methods without arguments. | ||
In order to provide arguments to the subscribed methods, a generic {{Link/Enfusion|armaR|ScriptInvokerBase}} type must be used, e.g <enforce inline>ScriptInvokerBase< | In order to provide arguments to the subscribed methods, a generic {{Link/Enfusion|armaR|ScriptInvokerBase}} type must be used, e.g <enforce inline>ScriptInvokerBase<func></enforce>. | ||
A method signature can be declared using {{hl|typedef}}: | A method signature can be declared using {{hl|typedef}}: |
Revision as of 21:16, 19 May 2023
A ScriptInvoker is an object that allows other objects to subscribe to the event it represents by registering a method. Such event can provide arguments and it is important for the subscribing methods to fit the proper method signature.
The interest of using Events is that the subscribed method is be executed only if and when a specific event occurs (e.g a fired weapon, someone leaving a vehicle, etc) - no periodical check is done, saving CPU cycles and executing exactly on event.
Usage
Signature Declaration
The ScriptInvoker class used above is the "default" one used for methods without arguments. In order to provide arguments to the subscribed methods, a generic ScriptInvokerBase type must be used, e.g ScriptInvokerBase<func>.
A method signature can be declared using typedef:
And used like this:
That's it! Remember that ScriptInvokers/Event Handlers are very powerful, but dangerous tools. Be sure not to fall into any trap or loop!