IOBluetooth: warn about incorrent thread/runloop

IOBluetooth is heavily based on CFRunLoops. An attempt to use it on a thread,
that does not properly run CFRunLoop results in callbacks never firing and
thus QBluetooth classes never finishing their jobs, including:

- device discovery
- service discovery
- RFCOMM/LCAP2
- Bluetooth server
- Bluetooth socket

etc.

While we cannot fix the core problem until we have a properly working
CoreFoundation event dispatcher, we can at least issue a warning so that
people do not waste their time debugging this well-known limitation.

Task-number: QTBUG-63630
Change-Id: Iefa4d675ea0962167bdfede640d2087dbdf37b18
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

0 files changed, 0 insertions, 0 deletions