diff options
authorOliver Wolff <>2019-05-07 15:09:00 +0200
committerAlex Blasche <>2019-07-24 06:48:34 +0000
commitc9d585da2ddd49108d7b56f480bcfc9d71b67dbf (patch)
parent8110fdd4c6d80d05934768fa808a4cb187212fe0 (diff)
winrt: Add limitations to bluetooth overview page
Same as on Android, Obex is not supported on winrt. Even though QBluetoothServiceInfo has a small passage about winrt's limitations when it comes to RFCOMM. Users might miss these limitations as they are quite hidden. Make them more visible by also having them in the overview. Task-number: QTBUG-62520 Change-Id: Ibdf1a9b334b7138301e833981e67c7813488bbd1 Reviewed-by: Alex Blasche <>
1 files changed, 6 insertions, 1 deletions
diff --git a/src/bluetooth/doc/src/bluetooth-overview.qdoc b/src/bluetooth/doc/src/bluetooth-overview.qdoc
index 8138e937..e27dc0ed 100644
--- a/src/bluetooth/doc/src/bluetooth-overview.qdoc
+++ b/src/bluetooth/doc/src/bluetooth-overview.qdoc
@@ -47,7 +47,12 @@
\li Receive advertisement from Bluetooth Low Energy device.
- Note that the Object Push Profile is not supported on Android.
+ Note that the Object Push Profile is not supported on Android and Windows.
+ Note that parts of RFCOMM functionality cannot be configured by Qt on Windows.
+ A service's \l {ServiceClassIds} and \l {ProtocolDescriptorList} are filled automatically by
+ Windows. Therefore registering a service with custom values for these fields might not yield the
+ expected result on Windows.
The following sections describe how to use the Qt Bluetooth C++ API classes
for the above use cases.