Windows Write Event Fix

[Cartermel]

• fixed issue where the WriteEvent from CharacteristicConfig was not being set to the internal winrt characteristic
• removed write event being called from the internal Characteristic.Write(), which was leading to an infinite loop when attempting to write to the characteristic in it's own write event

Not sure if the second point is intended behavour? In gatts_linux.go it calls a characterisit writeEvent, but I'm assuming bluez is writing to the characterisitic for you, whereas in winrt we have to write to it manually... One of these is probably not intended..!

[jagobagascon]

Note: I tried to test this but it seems that my bluetooth dongle does not support working as a peripheral.

The first point LGTM.

But I have some concerns about removing the write event call from Characteristic.Write().

I could not test this but checking the code I imagine the infinite loop also happens on linux. And if that's the case I would try to keep the behaviour consistent among the different platforms. Maybe @aykevl can confirm this? Is this intended behaviour?

@Cartermel maybe we could split this PR in two and merge the first part while we clarify if the infinite loop is intended behaviour or not? I think it's something we can live with (it can probably be avoided by setting some flag to ignore your own callbacks).

[Cartermel]

sounds good, created a new PR here with the windows changes for now: #277

[jagobagascon]

LGTM!

[jagobagascon]

@deadprogram is it fine if I merge this?

[deadprogram]

@jagobagascon looks good to me! Thanks @Cartermel for working on this.