Releases: Flowduino/EventDrivenSwift
Releases · Flowduino/EventDrivenSwift
5.2.0
5.1.0
Implemented .youngerThan Event Interest
EventListeners now support the.youngerThaninterested, specifying amaximumAgeparameter to define (in nanoseconds) the maximum age anEventablecan be (from the point of Dispatch) before the Listener is no longer interested in it.EventReceivingtypes (all of them) now also support the above behaviour.- README.md has been updated to provide an example of how to specify an
EventListenerwith a Maximum Age constraint.
5.0.0
- Introduced Latest-Only Listeners
- Introduced Latest-Only Receivers
dispatchTimeparameter added to all Callbacks (including Listeners) so that you can read the exact nanosecond-precise time at which each Event was Dispatched. Interface-breaking change, thus the major version increase- README.md updated to reflect all of the above
4.2.0
4.1.0
- Introduced
@EventMethodwrapper in bothEventThreadand any class implementingEventListening. Can now be used to register immutable Event Listener callbacks within the declaration of any class as avar, and invoke the methodregisterListeners()on theinitmethod of said class to automatically register any@EventMethod-decorated Listener using Reflection. - Replaced the returning of Tokens (
UUIDs) when registering an Event Listener, or an Event Callback (insideEventThread) with an appropriateHandletype, containing aremove()method to unregister said Listener/Callback.
4.0.2
4.0.1
- Certain
internalmethods have been marked asopenin order to make inheriting classes consuming the library function properly. This is due to a limitation in Swift whereby any inheriting class where the base class originates inside of a Library cannot accessinternalmembers defined in the Library.
4.0.0
Version 4.0.0 introduces considerable refactoring and interface changes:
EventReceivableis no longer a class to inherit from for your own Event Processing Threads.EventThreadis now the class to inherit from for your own Event Process Threads.- Nomenclature has been standardised throughout the library to eliminate any ambiguity between an
EventReceiver(which is a fundamental base type for anything which receivesEventableobjects. EventPooland all of its supporting types have been introduced as a major new feature for this release- README.MD has been fully updated to reflect all refactoring and feature changes introduced for this version.
3.0.1
EventListenerimplementation completedEventCentralupdated to provide a centralisedEventListenerfor global useEventableintroduces two new methods:addListenerregisters an arbitrary Listener against the referencedEventableType and returns aUUIDtoken for that ListenerremoveListenerunregisters the Listener specified by itsUUIDtoken
2.0.0
- Introduced
UIEventReceiver - Eliminated the need to implement a boilerplate Closure to invoke
callTypedEventCallbackin order to type-qualify anEventablefor a Callback call. This is now done internally for you. - Updated the README.MD file to reflect the above