diff options
| author | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-10-11 10:10:27 +0200 |
|---|---|---|
| committer | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-10-11 09:38:33 +0000 |
| commit | 4bce1481c5cfbd402973c2a488b36499ed44af2e (patch) | |
| tree | 545541267438228eeb6ee3f7895f16df79a943b9 /examples | |
| parent | cbf95d0ee78ad83cd26887670824e62678e4673e (diff) | |
| download | qtconnectivity-4bce1481c5cfbd402973c2a488b36499ed44af2e.tar.gz | |
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>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions