#4 UUID "clone" constructor bug

[Iain Price]

The constructor for the UUID type which takes a UUID as its parameter has an error in its singular line of code - the copy is backwards, meaning that rather than clone the supplied UUID into a new UUID, it blanks both of them to the null key.

Consequentially the static UUID.XOr(UUID,UUID) actually destroys the contents of the first UUID parameter passed.

Further consequentially, this destroys the ability of the entire instant message set of calls to send instant messages to anyone other than "themselves" (send to self works as it doesn't call the UUID XOR function).

That was fun... :P

[Frederick Martian]

Thanks for the report. Seems it got introduced some time ago when refactoring some of the libomv.types classes. A fix is commited to the SVN repository at this moment.