At present, the Event Engine requires that all Listeners be created as children of a TLKEventThread.
This leaves the implementing developer to define a TLKEventThread to dictate how best to update elements on their UI in a thread-safe way.
However, there is a reasonable solution which can enable an implementing developer to simply create a TLKEventListener without defining a TLKEventThread instance, and for that Listener's callback to be executed on the UI thread.
This should be introduced as it is going to be very useful for producing UI-specific Event Consumers without the need to have a companion Thread (if the implementing developer does not wish for one).
At present, the Event Engine requires that all Listeners be created as children of a
TLKEventThread.This leaves the implementing developer to define a
TLKEventThreadto dictate how best to update elements on their UI in a thread-safe way.However, there is a reasonable solution which can enable an implementing developer to simply create a
TLKEventListenerwithout defining aTLKEventThreadinstance, and for that Listener's callback to be executed on the UI thread.This should be introduced as it is going to be very useful for producing UI-specific Event Consumers without the need to have a companion Thread (if the implementing developer does not wish for one).