[cppcooper]

No description provided.

[myk002]

after this change, what will the options be for cpp and lua code to handle regular callbacks? will we be able to replace repeat-util with eventful?

[cppcooper]

after this change, what will the options be for cpp and lua code to handle regular callbacks? will we be able to replace repeat-util with eventful?

It looks as though that script could easily be replaced, yes.

edit:

As for options, cpp will have the registerTick and registerListener available for tick events. Most use cases will likely be opting for the registerListener unless they want the event to only trigger once. For example: if they need to run some clean up code.

eventful on the other hand, doesn't have tick events integrated.. but shouldn't be difficult to do.

edit2:

So I've tried to integrate tick events to eventful. It needs a bit of testing, but I believe it has all the same boilerplate the other event types have (so it should work, unless I missed something). It will only rely on the registerListener the same as the others. Of course this precludes it from the other functionality available with registerTick. So if a callback needs to happen only once, the user would then need to unregister the listener inside their callback.

[cppcooper]

after this change, what will the options be for cpp and lua code to handle regular callbacks? will we be able to replace repeat-util with eventful?

As discussed on discord, there are a few technical challenges when bringing tick events to lua. So I reverted those changes.

I've included an updated channel-safely in this PR which uses the newly repeating tick events to perform some tasks. Additionally I had added a temporary event which repeated hourly and performed a test to ensure the tick listener events are refiring without any user effort. [test was successful]

[ab9rf]

This PR appears abandoned and code has drifted considerably since it was last touched.