I ma trying to figure out the most appropriate implementation of comms via bluetooth using the Ketai library.

When I see the KetaiBluetooth::start() method, I imagine that the bluetooth object is in fact a separate thread? Is that correct?

When I want to write to the bluetooth device, should I spawn my own thread, to exit the main animation thread, or does the call 'KetaiBluetooth::writeToDeviceName(...)' already create a wake-up event on the Ketai thread?

I have implemented both versions but cannot tell from execution and traces what is going on, nor which is the appropriate implementation?

Anyone have any ideas?

Thanks,
Bob