Before the "Big Redux" (redevelopment of the Event Engine from the ground up), TLKEventListener provided a property called LatestOnly, which defined whether or not Events dispatched prior to the last one processed by that Listener should be processed by said Listener.
By default, Listeners don't care about the order of execution, but there are situations in which an implementation may want to ensure that only the latest Event of a given type is processed, and any older Event received after that is ignored.
This matters because of Stack Order Processing (where Events may be processed in reverse order, where a newer Event supersedes the data provided by any earlier instance of that Event type).
LaKraven
commented
9 years ago
Before the "Big Redux" (redevelopment of the Event Engine from the ground up),
TLKEventListenerprovided a property calledLatestOnly, which defined whether or not Events dispatched prior to the last one processed by that Listener should be processed by said Listener.By default, Listeners don't care about the order of execution, but there are situations in which an implementation may want to ensure that only the latest Event of a given type is processed, and any older Event received after that is ignored.
This matters because of Stack Order Processing (where Events may be processed in reverse order, where a newer Event supersedes the data provided by any earlier instance of that Event type).