From 26840646bb0e1b82bb6608395ba6041538ced3ab Mon Sep 17 00:00:00 2001 From: Alex Blasche Date: Thu, 18 Oct 2018 09:09:30 +0200 Subject: Improve QBluetoothDeviceDiscoveryAgent::deviceDiscovered() docs The previous definition was not aware of the new deviceUpdated() signal. This patch better outlines the connection. Change-Id: I8beee9b43c5c0b782676de61b27b219b32c245f5 Reviewed-by: Timur Pocheptsov --- src/bluetooth/qbluetoothdevicediscoveryagent.cpp | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) (limited to 'src/bluetooth/qbluetoothdevicediscoveryagent.cpp') diff --git a/src/bluetooth/qbluetoothdevicediscoveryagent.cpp b/src/bluetooth/qbluetoothdevicediscoveryagent.cpp index cdb3d5d7..c9c3fa39 100644 --- a/src/bluetooth/qbluetoothdevicediscoveryagent.cpp +++ b/src/bluetooth/qbluetoothdevicediscoveryagent.cpp @@ -138,10 +138,11 @@ Q_DECLARE_LOGGING_CATEGORY(QT_BT) The signal is emitted as soon as the most important device information has been collected. However, as long as the \l finished() signal has not been emitted the information collection continues even for already discovered - devices. This is particularly true for signal strength information (RSSI). If - signal strength information is required it is advisable to retrieve the device - information via \l discoveredDevices() once the discovery has finished. This - will yield the most recent RSSI information. + devices. This is particularly true for signal strength information (RSSI) and + manufacturer data updates. If the use case requires continuous manufacturer data + or RSSI updates it is advisable to retrieve the device information via + \l discoveredDevices() once the discovery has finished or listen to the + \l deviceUpdated() signal. If \l lowEnergyDiscoveryTimeout() is larger than 0 the signal is only ever emitted when at least one attribute of \a info changes. This reflects the desire to -- cgit v1.2.3