BluetoothManager: Utilize own glib main context and associate it with the main loop

At Zafena (Issue #14), we experienced that the BluetoothGattCharacteristic callbacks '::on_properties_changed_characteristic'
were not handled by BluetoothManager's own main loop thread, but passed via the 'JavaFX Main Application Thread'.

BluetoothManager already utilizes its own main loop thread and it looks like
it only has to register its own main context and associate it and use it as the thread local default context.

This seems to be sufficient to have all other callbacks being handled from its own main loop thread.

0 files changed, 0 insertions, 0 deletions