Releases: orchetect/OSCKit
Releases · orchetect/OSCKit
2.0.1
2.0.0
Note
This release contains various minor API changes, as well as bug fixes and other refinements. As such, it has gained a major version number bump to version 2.
A summary of the main changes can be found below.
- OSCKitCore
OSCObjectprotocol has been removed since the only two concrete types that can possibly conform areOSCBundleorOSCMessage.- The protocol has been replaced a new
OSCPacketenum that contains two strongly-typed cases containing either anOSCBundleorOSCMessage.
- The protocol has been replaced a new
OSCPacketandOSCBundle: Both have a newmessagesproperty that returns an array ofOSCMessages contained within the packet or bundle.OSCAddressSpace: Converted class into an actorOSCAddressSpace: Added newunregister(methodID:)methodOSCEncodeErrorandOSCDecodeError: Now have more idiomatic error cases- Throwing methods that throw a strongly-typed error are now marked as such in the method signature
- OSCKit
OSCUDPServer:init: Passingnilor0forportparameter will now cause a random available port number to be used- This also fixes a bug where the
localPortproperty was not updated if a random port was assigned
- This also fixes a bug where the
OSCUDPClient:init: Passingnilor0forlocalPortparameter will now cause a random available port number to be usedOSCTCPServer:init: Passingnilor0forportparameter will now cause a random available port number to be used
1.4.1
1.4.0
1.3.0
New
- TCP client and server classes have been added:
OSCTCPClient&OSCTCPServer- supporting OSC 1.0 (PLH) and OSC 1.1 (SLIP) framing modes
- connection/disconnection notification handler
- optionally constrain communication to a specific network interface
- A new TCP Client and Server example project has been added
- The existing UDP classes now also gain an
interfaceproperty to optionally constrain communication to a specific network interface
Fixes
- Fixed bug in OSC value parser where a crash could happen in rare cases
Changes
OSCClientclass has been renamedOSCUDPClientto disambiguate from the new TCP classesOSCServerclass has been renamedOSCUDPServerto disambiguate from the new TCP classesOSCSocketclass has been renamedOSCUDPSocketto disambiguate from the new TCP classes- Some class properties have been renamed for better clarity or consistency.
1.2.2
1.2.1
New
AnyOSCNumberValue: AddedBoolas a boxable type (#47)AnyOSCNumberValue: AddedboolValuecomputed property (#47)OSCValueToken: AddednumberOrBoolandnumberOrBoolOptionalcases (#47)
Maintenance
- Updated SPI to remove watchOS from README platform badges (#46)
- Updated documentation to reflect changes
- Updated unit tests
1.2.0
1.1.0
1.0.1
Fixes
OSCServer/OSCSocket/OSCClient: Fixed regression where newly immutable properties were not added as initializer parameters
Deprecations
OSCServer/OSCSocket: RemovedisPortReuseEnabledproperty as it has no effect on Apple platforms
Maintenance
- Rebuilt all example projects as SwiftUI apps
- Example projects now build for all platforms (macOS, iOS, tvOS, visionOS) and can be run in simulators