Implement booleans

[s-ol]

The boolean type tags are listed in the wiki but don't actually work:

• TypedMessage.pack doesn't implement them
• TypedMessage.unpack implements them wrongly (will end the message if it encounters a boolean)
• typeTag doesn't implement them, meaning Message.add can't use them

Also, while in the OSC protocol booleans take no space in the message encoding, I think it would be beneficial to add true/false values into TypedMessage.args at the corresponding position. Otherwise the mapping from type to args is broken, which means the user has to essentially re-parse the type string just to find the corresponding value.

[adzialocha]

Oh, thanks for the note @s-ol, think I've overlooked this one when merging #48.

@davidgranstrom, maybe you have an idea what is missing?

[davidgranstrom]

@s-ol @adzialocha I think that adding corresponding values for the T,F (and I,N) types in order to keep symmetry between args and typetag makes sense.

It was a while since I wrote the PR so I would have to take a closer look to see what is actually needed. But I think it is mainly about adding the values in Message.unpack when looping over the typetag string and also accept values in the typeTag helper function. I don't think Message.pack would need to implement this since these types are not part of the binary OSC message data.

[adzialocha]

Thank you @davidgranstrom !

I had a go on an implementation here, please have a look if you have time: #59

[davidgranstrom]

@adzialocha That was fast :) Looks good to me! 👍

[adzialocha]

Super, lets release it then!