v0.14.0

Yesterday, I declared the deprecation of the generic Packet, but embarrassingly, I'm going to resurrect it. Well, to be precise, I will rather make the Packet added in the previous release generic (Packet<TValue>). This will allow us to regain the type safety sacrificed in the previous release.

Since I'm removing the APIs deprecated in v0.13.1, transitioning from v0.12.0 will involve more breaking changes. Here's how the syntax will differ:

// v0.12.0
StringPacket stringPacket = new StringPacket("Hello World!", new TimeStamp(0));
var value = stringPacket.Get();
stringPacket.GetInt(); // compile error

var intPacket = new IntPacket();

// v0.13.1
Packet stringPacket = Packet.CreateStringAt("Hello World!", 0);
var value = stringPacket.GetString();
stringPacket.GetInt(); // runtime error

var intPacket = new Packet();

// v0.14.0
Packet<string> stringPacket = Packet.CreateStringAt("Hello World!", 0);
var value = stringPacket.Get();
stringPacket.GetInt(); // compile error

var intPacket = new Packet<int>();

ATTENTION: For some reason, the iOS framework is no longer included in the unitypackage, so if you need the iOS library, please use the tarball version or build it by yourself. MediaPipeUnityPlugin-all-stripped.zip also contains the iOS library.

⚠️ BREAKING CHANGES

• strongly-typed Packet, once again (#1120)
• remove deprecated APIs (#1119)

See CHANGELOG for more details.