YEA, sdk.execute is the proper way...
i never thought anyone would hijack a ONxxxx Event :)
reminds me, must look to see if there is anything else my plugins hijack. hmmm.
commands that are events "ONxxxx" are sent to all plugins, even if there is a translation in exectable...
like if someone did "ONSUSPEND","blablabla" in exectble
all plugins would still see "ONSUSPEND", so they could do what they need to do
this was added back, when i noticed the exectbl consuming my events
and then plugins failed
so ONxxxx commands, are processed slightly different, and didnt have any return check for processcommand=3 or such...
I never thought anyone would "hijack" em
"hijacking" is OK now...
I still say for the "ONxxxx" types its best to do execute(....)
for normal commands... feel free to hijack...
but now in the new code, there is code to allow the "onxxx" to be hijacked
and still have all plugins see the origional "Onxxxx" event
its that 1000 ways to skin a cat deal
Strange how it worked OK in the last RoadRunner though :p
Yeah, it stopped working when we "Improved" it so all plugins would be notified -- in RoadRunner if the plugin hijacked the event, any other plugin waiting for the same event would not get it. With the second improvement now, both things should work :)
Originally Posted by Enforcer
Thanks for the quick response on this guys.
OK John, you can continue to test and skin RRTC. ;)