Actually updated plugin version number to 0.2.5.

v0.2.5 - This update includes three changes, none of which are likely to be noticeable to the user.

First, rather than separating bundles into individual messages on the async thread and feeding them to the main thread one at a time, bundles are passed through to the main thread in whole. Most importantly, this ensures atomicity of bundles (per the OSC spec). All of the messages in a bundle are guaranteed to be processed on the same frame, and no other messages can be interspersed in the bundle. This also has the side effect of making it easier to implement bundle time tags in the future to "schedule" a bundle, but that hasn't been implemented yet.

Second, data output port changes are reduced, such that rather than recreating all data output ports every time an argument type changes, only the affected ports are recreated.

Finally, an unnecessary `Broadcast` on the input node is removed when processing a received message. This was incurring a large performance cost in serializing the node every time a message is received, but it's entirely unnecessary and has been fixed. Thanks to @TigerHix for pointing this out!

v0.2.4 - Added type coercion of arguments.

Bool <- Double/Float/Int/Long - 0/NaN is false, anything else is true

Float <- Bool - True is 1, false is 0
Float <- Int - Best-attempt conversion (i.e. a cast)

Int <- Bool - True is 1, false is 0
Int <- Float - Rounded to the nearest integer, then best-attempt conversion (i.e. a cast)

Strings are not coerced from/to any other type.

v0.2.3 - Added support for wildcards in message addresses, per the OSC spec.

v0.2.2 - Swapped an outdated, unmaintained OSC library for a more recent one. This fixes issues with certain types of messages (no arguments or only boolean arguments) being ignored. It should also improve performance (though I haven't measured that).

v0.2.1 - This release is changes to the internals only. There should be no functional changes.

Message dispatching is added at the Plugin level, meaning that only On OSC Message nodes configured with the correct address will process any received OSC message. This could result in better performance in the event that there are a lot of OSC nodes with different addresses, but will most likely not be a significant difference with reasonable numbers of OSC nodes.

v0.2.0 - Reworked the "OSC Input" node into the "On OSC Message" node, which allows for simpler reading of any number of arguments. This should make the node simpler to use and more versatile, as I learn more about how to create plugins for Warudo!

This new node is not compatible with the old one, so this is a breaking change! Any instances of the old node will disappear. This plugin is currently still unlisted, so that shouldn't be an issue for now.

v0.1.0 - Created in Warudo