diff options
Diffstat (limited to 'src/bluetooth/doc/src')
| -rw-r--r-- | src/bluetooth/doc/src/bluetooth-cpp.qdoc | 31 | ||||
| -rw-r--r-- | src/bluetooth/doc/src/bluetooth-index.qdoc | 156 | ||||
| -rw-r--r-- | src/bluetooth/doc/src/bluetooth-le-overview.qdoc | 68 | ||||
| -rw-r--r-- | src/bluetooth/doc/src/bluetooth-overview.qdoc | 51 | ||||
| -rw-r--r-- | src/bluetooth/doc/src/bluetooth-qml.qdoc | 48 | ||||
| -rw-r--r-- | src/bluetooth/doc/src/examples.qdoc | 47 |
6 files changed, 109 insertions, 292 deletions
diff --git a/src/bluetooth/doc/src/bluetooth-cpp.qdoc b/src/bluetooth/doc/src/bluetooth-cpp.qdoc index 26cd060b..958609bf 100644 --- a/src/bluetooth/doc/src/bluetooth-cpp.qdoc +++ b/src/bluetooth/doc/src/bluetooth-cpp.qdoc @@ -1,29 +1,5 @@ -/**************************************************************************** -** -** Copyright (C) 2017 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt local connectivty modules. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ +// Copyright (C) 2017 The Qt Company Ltd. +// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only /*! \module QtBluetooth @@ -36,8 +12,7 @@ The \l{Qt Bluetooth} C++ API enables an application to scan for devices and - connect and interact with them in a more flexible way than the \l {Qt - Bluetooth QML Types}. + connect and interact with them in a more flexible way. To use the C++ library in your application, add the following configuration option to your \c .pro file: diff --git a/src/bluetooth/doc/src/bluetooth-index.qdoc b/src/bluetooth/doc/src/bluetooth-index.qdoc index 0f5b96d6..ff6bf037 100644 --- a/src/bluetooth/doc/src/bluetooth-index.qdoc +++ b/src/bluetooth/doc/src/bluetooth-index.qdoc @@ -1,29 +1,5 @@ -/**************************************************************************** -** -** Copyright (C) 2019 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt Toolkit. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ +// Copyright (C) 2022 The Qt Company Ltd. +// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only /*! \page qtbluetooth-index.html @@ -40,10 +16,9 @@ Currently, the API is supported on the following platforms: \li API Feature \li \l {Qt for Android}{Android} \li \l {Qt for iOS}{iOS} - \li \l {Qt for Linux/X11}{Linux (BlueZ 4.x/5.x)} + \li \l {Qt for Linux/X11}{Linux (BlueZ 5.x)} \li \l \macos - \li \l {Qt for UWP}{UWP (Universal Windows Platform)} - \li \l {Qt for Windows}{Win32} + \li \l {Qt for Windows}{Windows} \row \li Classic Bluetooth \li x @@ -51,7 +26,6 @@ Currently, the API is supported on the following platforms: \li x \li x \li x - \li x \row \li Bluetooth LE Central \li x @@ -59,7 +33,6 @@ Currently, the API is supported on the following platforms: \li x \li x \li x - \li x \row \li Bluetooth LE Peripheral \li x @@ -67,67 +40,86 @@ Currently, the API is supported on the following platforms: \li x \li x \li - \li -\row - \li Bluetooth LE Advertisement & Scanning - \li - \li - \li - \li - \li - \li \endtable -Qt 5.14 adds a native Win32 port supporting Classic Bluetooth on Windows 7 or newer, -and Bluetooth LE on Windows 8 or newer. It must be enabled at build time by configuration -option -native-win32-bluetooth. The UWP backend is used by default if this option is not -set and the Win32 target platform supports the required UWP APIs (minimal requirement is -Windows 10 version 1507, with slightly improved service discovery since Windows 10 version -1607). - \section1 Overview Bluetooth is a short-range (less than 100 meters) wireless technology. It -has a reasonably high data transfer rate of 2.1 Mbit/s, which makes it ideal +has a data transfer rate of 2.1 Mbps, which makes it ideal for transferring data between devices. Bluetooth connectivity is based on basic device management, such as scanning for devices, gathering information about them, and exchanging data between them. -Qt Bluetooth supports Bluetooth Low Energy development for client/central role use cases. -Further details can be found in the +Qt Bluetooth supports Bluetooth Low Energy development for client/central role +use cases. Further details can be found in the \l {Bluetooth Low Energy Overview}{Bluetooth Low Energy Overview} section. -A new addition since the Qt Bluetooth 5.7 release covers support for Bluetooth Low Energy -applications performing the peripheral/server role. This new API remains in Technology Preview. +\section1 Using the Module + +\include {module-use.qdocinc} {using the c++ api} + +\section2 Building with CMake -\section1 Getting Started +\include {module-use.qdocinc} {building with cmake} {Bluetooth} -To use the C++ library in your application, add the following configuration -option to your \c .pro file: +\section2 Building with qmake -\snippet snippets.pro contacts project modification +\include {module-use.qdocinc} {building_with_qmake} {bluetooth} -To use the classes of the module in your application you need the following -import statement in your \c .qml file: +\section1 Permissions -\snippet doc_src_qtbluetooth.qml import +Starting from Qt 6.6, the Qt Bluetooth module uses new \l QPermission API +to handle \l {QBluetoothPermission}{Bluetooth} permissions. This means that Qt +itself no longer queries for these permissions, so this needs to be done +directly from the client application. + +Please refer to the \l {Application Permissions} page for an example of how +to integrate the new \l QPermission API into the application. \section1 Related Information \section2 Building Qt Bluetooth -Despite the fact that the module can be built for all Qt platforms, -the module is not ported to all of them. Not supported platforms -employ a fake or dummy backend which is automatically selected when the -platform is not supported. The dummy backend reports appropriate error messages -and values which allow the Qt Bluetooth developer to detect at runtime that the -current platform is not supported. The dummy backend is also selected on Linux if -BlueZ development headers are not found during build time or Qt was built without -Qt D-Bus support. +Even though the module can be built for all Qt platforms, the module is not +ported to all of them. Non-supported platforms employ a dummy backend that is +automatically selected when the platform is not supported. The dummy backend +reports appropriate error messages and values, which enables you to detect at +runtime that the current platform is not supported. The dummy backend is also +selected on Linux if BlueZ development headers are not found during build time +or Qt was built without Qt D-Bus support. The usage of the dummy backend is highlighted via an appropriate warning while building and running. -\section2 Guides +\section3 Linux Specific + +Since Qt 6.5 the Linux peripheral support has two backend alternatives: +BlueZ DBus and Bluetooth Kernel API. The DBus backend is the default +backend since Qt 6.7. + +BlueZ DBus is the newer BlueZ stack and possibly the eventual successor of the +older Kernel API. It is a bit more limited in terms of features, but in a +typical usage this should not matter. One notable benefit of using the DBus +backend is that the user process no longer needs to have the +\e CAP_NET_ADMIN capability (for example by running as \c root user). + +The DBus backend requires BlueZ version 5.56 or higher, and that it provides +the needed DBus APIs. If these requirements are not met, Qt automatically +falls back to the Bluetooth Kernel API backend. + +The older kernel backend can also be selected manually by setting the +\e QT_BLUETOOTH_USE_KERNEL_PERIPHERAL environment variable. + +\section3 \macos Specific +The Bluetooth API on \macos requires a certain type of event dispatcher +that in Qt causes a dependency to \l QGuiApplication. However, you can set the +environment variable \c {QT_EVENT_DISPATCHER_CORE_FOUNDATION=1} to circumvent +this issue. + +Applications that don't use Classic Bluetooth will find a subset of QtBluetooth +is available, as CoreBluetooth (Bluetooth LE) don't require \l QApplication or +\l QGuiApplication. + +\section2 Articles and Guides \list \li \l {Qt Bluetooth Overview}{Classic Bluetooth Overview} \li \l {Bluetooth Low Energy Overview} @@ -135,7 +127,6 @@ The usage of the dummy backend is highlighted via an appropriate warning while b \section2 Reference \list - \li \l {Qt Bluetooth QML Types}{QML Types} \li \l {Qt Bluetooth C++ Classes}{C++ Classes} \endlist @@ -164,20 +155,14 @@ The \l QtBluetooth module exports the following \li qt.bluetooth.osx \li Enables logging of the \l {Qt for macOS} {macOS} implementation \row - \li qt.bluetooth.qml - \li Enables logging of the QtBluetooth QML implementation -\row - \li qt.bluetooth.winrt - \li Enables logging of the \l {Qt for UWP}{UWP (Universal Windows Platform)} - implementation -\row \li qt.bluetooth.windows - \li Enables logging of the \l {Qt for Windows} {Win32} implementation + \li Enables logging of the \l {Qt for Windows} {Windows} implementation \endtable -Logging categories can be used to enable additional warning and debug output -for QtBluetooth. More detailed information about logging can be found in \l QLoggingCategory. -A quick way to enable all QtBluetooth logging is to add the following line to the \c main() function: +Logging categories enable additional warning and debug output for QtBluetooth. +More detailed information about logging is found in \l QLoggingCategory. A +quick way to enable all QtBluetooth logging is to add the following line to the +\c main() function: \code QLoggingCategory::setFilterRules(QStringLiteral("qt.bluetooth* = true")); @@ -187,10 +172,6 @@ A quick way to enable all QtBluetooth logging is to add the following line to th \list \li QML \list - \li \l {scanner}{QML Bluetooth Scanner} - \li \l {picturetransfer}{QML Bluetooth Picture Push} - \li \l {pingpong}{QML Bluetooth PingPong} - \li \l {chat}{QML Bluetooth Chat} \li \l {heartrate-game}{Bluetooth Low Energy Heart Rate Game} \li \l {heartrate-server}{Bluetooth Low Energy Heart Rate Server} \li \l {lowenergyscanner}{Bluetooth Low Energy Scanner} @@ -198,11 +179,14 @@ A quick way to enable all QtBluetooth logging is to add the following line to th \li C++ \list \li \l {btchat}{Bluetooth Chat} - \li \l {btscanner}{Bluetooth Scanner} - \li \l {btfiletransfer}{Bluetooth File Transfer} \endlist \endlist +\section1 Module Evolution + +\l{Changes to Qt Bluetooth} lists important changes in the module +API and functionality that were done for the Qt 6 series of Qt. + \section1 Licenses and Attributions Qt Bluetooth is available under commercial licenses from \l{The Qt Company}. diff --git a/src/bluetooth/doc/src/bluetooth-le-overview.qdoc b/src/bluetooth/doc/src/bluetooth-le-overview.qdoc index 60181240..cc943088 100644 --- a/src/bluetooth/doc/src/bluetooth-le-overview.qdoc +++ b/src/bluetooth/doc/src/bluetooth-le-overview.qdoc @@ -1,29 +1,5 @@ -/**************************************************************************** -** -** Copyright (C) 2017 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt local connectivty modules. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ +// Copyright (C) 2017 The Qt Company Ltd. +// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only /*! \ingroup technology-apis @@ -34,11 +10,9 @@ Low Energy devices. \tableofcontents - The Qt Bluetooth Low Energy API for the central role was introduced by Qt 5.4. - Since Qt 5.5 that part of the API is final and a compatibility guarantee is given for - future releases. - Since Qt 5.7, additional API supporting the peripheral role was added as a Technology Preview, - with the backend implemented for Linux/BlueZ, iOS and macOS. + The Qt Bluetooth Low Energy API supports the peripheral/server and central/client roles. + It is supported on all major Qt platforms. The only exception is the missing peripheral role + support on Windows. \section1 What Is Bluetooth Low Energy @@ -120,7 +94,7 @@ Low Energy devices. \row \li 0x0004 \li 0x2803 - \li UUID 0x2A08, Value handle: 0x0006 + \li UUID 0x2A08, Value handle: 0x0005 \li Characteristic of type Date Time \row \li 0x0005 @@ -146,7 +120,7 @@ Low Energy devices. The example above uses the UUIDs \c 0x2A08 (Date Time) and \c 0x2A37 (Heart Rate Measurement). Each of the above UUIDs is defined by the \l {https://bluetooth.org}{Bluetooth Special Interest Group}. and can be found in the - \l{https://developer.bluetooth.org/gatt/Pages/default.aspx}{GATT specification}. While it + \l{https://www.bluetooth.com/specifications/assigned-numbers}{GATT specifications}. While it is advisable to use pre-defined UUIDs where available it is entirely possible to use new and not yet used UUIDs for characteristic and service types. @@ -181,7 +155,10 @@ Low Energy devices. Since we are only interested in Low Energy devices we filter the device type within the receiving slot. The device type can be ascertained using the \l QBluetoothDeviceInfo::coreConfigurations() - flag: + flag. The \l {QBluetoothDeviceDiscoveryAgent::}{deviceDiscovered()} signal + may be emitted multiple times for the same device as more details are + discovered. Here we match these device discoveries so that the user only + sees the individual devices: \snippet heartrate-game/devicefinder.cpp devicediscovery-3 \snippet heartrate-game/devicefinder.cpp devicediscovery-4 @@ -197,13 +174,13 @@ Low Energy devices. \section2 Service Search - The above code snippet how the application initiates the service discovery once the connection has - been established. + The above code snippet shows how the application initiates the service discovery once the + connection has been established. The \c serviceDiscovered() slot below is triggered as a result of the \l {QLowEnergyController::serviceDiscovered()} signal and provides an intermittent progress report. Since we are talking about the heart listener app which monitors HeartRate devices in the vicinity - we ignore any service that is not of type \l QBluetoothUuid::HeartRate. + we ignore any service that is not of type \l QBluetoothUuid::ServiceClassUuid::HeartRate. \snippet heartrate-game/devicehandler.cpp Filter HeartRate service 1 @@ -216,21 +193,21 @@ Low Energy devices. \snippet heartrate-game/devicehandler.cpp Filter HeartRate service 2 During the detail search the service's \l {QLowEnergyService::state()}{state()} transitions - from \l {QLowEnergyService::DiscoveryRequired}{DiscoveryRequired} to - \l {QLowEnergyService::DiscoveringServices}{DiscoveringServices} and eventually ends with - \l {QLowEnergyService::ServiceDiscovered}{ServiceDiscovered}: + from \l {QLowEnergyService::RemoteService}{RemoteService} to + \l {QLowEnergyService::RemoteServiceDiscovering}{RemoteServiceDiscovering} and eventually ends with + \l {QLowEnergyService::RemoteServiceDiscovered}{RemoteServiceDiscovered}: \snippet heartrate-game/devicehandler.cpp Find HRM characteristic \section2 Interaction with the Peripheral Device In the code example above, the desired characteristic is of type - \l {QBluetoothUuid::HeartRateMeasurement}{HeartRateMeasurement}. Since the application measures + \l {QBluetoothUuid::CharacteristicType::HeartRateMeasurement}{HeartRateMeasurement}. Since the application measures the heart rate changes, it must enable change notifications for the characteristic. Note that not all characteristics provide change notifications. Since the HeartRate characteristic has been standardized it is possible to assume that notifications can be received. Ultimately \l QLowEnergyCharacteristic::properties() must have the \l {QLowEnergyCharacteristic::Notify} flag - set and a descriptor of type \l {QBluetoothUuid::ClientCharacteristicConfiguration} must exist to confirm + set and a descriptor of type \l {QBluetoothUuid::DescriptorType::ClientCharacteristicConfiguration} must exist to confirm the availability of an appropriate notification. Finally, we process the value of the HeartRate characteristic, as per Bluetooth Low Energy standard: @@ -286,4 +263,11 @@ Low Energy devices. In general characteristic and descriptor value updates on the peripheral device use the same methods as connecting Bluetooth Low Energy devices. + + \note To use \l{Qt Bluetooth} (in both central and peripheral roles) on iOS, you have to provide + an Info.plist file containing the usage description. According to the CoreBluetooth's + documentation: \e {Your app will crash if its Info.plist doesn’t include usage description + keys for the types of data it needs to access. To access Core Bluetooth APIs on apps linked + on or after iOS 13, include the NSBluetoothAlwaysUsageDescription key. In iOS 12 and earlier, + include NSBluetoothPeripheralUsageDescription to access Bluetooth peripheral data.} */ diff --git a/src/bluetooth/doc/src/bluetooth-overview.qdoc b/src/bluetooth/doc/src/bluetooth-overview.qdoc index 33ccaa33..54a429dc 100644 --- a/src/bluetooth/doc/src/bluetooth-overview.qdoc +++ b/src/bluetooth/doc/src/bluetooth-overview.qdoc @@ -1,29 +1,5 @@ -/**************************************************************************** -** -** Copyright (C) 2017 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt local connectivty modules. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ +// Copyright (C) 2017 The Qt Company Ltd. +// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only /*! \ingroup technology-apis @@ -49,12 +25,13 @@ 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. + \note Parts of RFCOMM functionality cannot be configured by Qt on + Windows. A service's \l {QBluetoothServiceInfo::}{ServiceClassIds} and + \l {QBluetoothServiceInfo::}{ProtocolDescriptorList} are filled + automatically. Therefore, registering a service with custom values for + these fields might not yield the expected result on Windows. - Note that the Received Signal Strength Indicator (RSSI), as well as + \note The Received Signal Strength Indicator (RSSI), as well as the Manufacturer Specific Data advertised by Bluetooth LE devices are not supported by the Win32 backend. Also, it is only possible to find devices that have been previously paired through Windows Settings. @@ -81,18 +58,6 @@ \snippet doc_src_qtbluetooth.cpp device_discovery - \section1 Pushing Files to Remote Devices - - Once the desired device was found, there are two main use cases provided by Qt Bluetooth. The - simpler one is to send files via the Obex Object Push Profile (OPP). As the name describes, this - profile can push files from one device to another. Currently it is not possible to pull files - or browse the remote file system. The profile does not require the two devices to be - paired before exchanging data. To push files to remote devices, create a - QBluetoothTransferRequest and ask the QBluetoothTransferManager to push the file contained in - the request by calling its \l {QBluetoothTransferManager::put()}{put()} function. - - \snippet doc_src_qtbluetooth.cpp sendfile - \section1 Exchanging Data Between Devices The more flexible approach for communication between two Bluetooth enabled devices, is to diff --git a/src/bluetooth/doc/src/bluetooth-qml.qdoc b/src/bluetooth/doc/src/bluetooth-qml.qdoc deleted file mode 100644 index a6870864..00000000 --- a/src/bluetooth/doc/src/bluetooth-qml.qdoc +++ /dev/null @@ -1,48 +0,0 @@ -/**************************************************************************** -** -** Copyright (C) 2017 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt local connectivty modules. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ - - -/*! - -\qmlmodule QtBluetooth \QtVer -\title Qt Bluetooth QML Types -\ingroup qmlmodules -\brief Provides QML types for basic Bluetooth operations on devices. - -The Qt Bluetooth QML Types enable an application to scan for devices and connect -and interact with them in an easier way than the C++ Classes. However, it is a bit -more limited than the C++ API. You can always use the C++ API to create QML -plugins with the flexibility you need. - -To use the classes of the module in your application you need the following -import statement in your \c .qml file: - -\qml \QtVer -import QtBluetooth \1 -\endqml -*/ - diff --git a/src/bluetooth/doc/src/examples.qdoc b/src/bluetooth/doc/src/examples.qdoc index e33ae4d8..46425cf6 100644 --- a/src/bluetooth/doc/src/examples.qdoc +++ b/src/bluetooth/doc/src/examples.qdoc @@ -1,32 +1,7 @@ -/**************************************************************************** -** -** Copyright (C) 2017 The Qt Company Ltd. -** Contact: https://www.qt.io/licensing/ -** -** This file is part of the documentation of the Qt Toolkit. -** -** $QT_BEGIN_LICENSE:FDL$ -** Commercial License Usage -** Licensees holding valid commercial Qt licenses may use this file in -** accordance with the commercial license agreement provided with the -** Software or, alternatively, in accordance with the terms contained in -** a written agreement between you and The Qt Company. For licensing terms -** and conditions see https://www.qt.io/terms-conditions. For further -** information use the contact form at https://www.qt.io/contact-us. -** -** GNU Free Documentation License Usage -** Alternatively, this file may be used under the terms of the GNU Free -** Documentation License version 1.3 as published by the Free Software -** Foundation and appearing in the file included in the packaging of -** this file. Please review the following information to ensure -** the GNU Free Documentation License version 1.3 requirements -** will be met: https://www.gnu.org/licenses/fdl-1.3.html. -** $QT_END_LICENSE$ -** -****************************************************************************/ +// Copyright (C) 2017 The Qt Company Ltd. +// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only /*! - \ingroup all-examples \page bluetooth-examples.html \title Qt Bluetooth Examples \brief Examples for the Qt Bluetooth module. @@ -47,12 +22,6 @@ \row \li \l{btchat}{Bluetooth Chat} \li Simple chat server and client via Bluetooth. - \row - \li \l{btfiletransfer}{Bluetooth File Transfer} - \li Transfer files between Bluetooth devices. - \row - \li \l{btscanner}{Bluetooth Scanner} - \li Scan for Bluetooth devices. \endtable \section2 QML Examples @@ -61,18 +30,6 @@ \li Example \li Description \row - \li \l{chat}{QML Bluetooth Chat Example} - \li Simple chat client via Bluetooth. - \row - \li \l{picturetransfer}{QML Bluetooth Picture Push Example} - \li Transfer pictures between Bluetooth devices. - \row - \li \l{pingpong}{QML Bluetooth PingPong} - \li Ping pong game demonstrating Bluetooth socket communication between two devices. - \row - \li \l{scanner}{QML Bluetooth Scanner} - \li Scan for Bluetooth devices and services. - \row \li \l{heartrate-game}{QML Bluetooth Low Energy Heart Rate Game} \li Connect to Bluetooth Low Energy heart rate belts and receive measurements such as the current pulse. |