Can Kross handle scripts that run throughout an application? Instead of execute then stop? And one last question. If so how can I go about doing that?
- once Action::trigger() was called, the script doesn't 'stop' but waits for something you like to do with it like e.g. calling a function, evaluating code or whatever. The script stops once Action::finalize() is called.
This page was last modified on 8 March 2009, at 18:34. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2
unless otherwise noted.