From 5c2f4d3472630be3a7b35c136434df5e8b50928f Mon Sep 17 00:00:00 2001 From: Alex Blasche Date: Fri, 11 Apr 2014 14:58:52 +0200 Subject: Fix inconsistent behavior between BtDiscoveryModel & BtServiceDiscoveryAgent The model always resets the model content when starting a new service discovery. However QBluetoothServiceDiscovery doesn't do that. It adds newly discovered services and maintains the existing services. Since the model updates its content based on the serviceDiscovered signal, every second run created an empty list or only ever added services. Change-Id: I9c1d29562b9178678ab42bee98d5d1e3d0c4367f Reviewed-by: Fabian Bumberger --- src/imports/bluetooth/qdeclarativebluetoothdiscoverymodel.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/src/imports/bluetooth/qdeclarativebluetoothdiscoverymodel.cpp b/src/imports/bluetooth/qdeclarativebluetoothdiscoverymodel.cpp index 842d042d..d042bdfe 100644 --- a/src/imports/bluetooth/qdeclarativebluetoothdiscoverymodel.cpp +++ b/src/imports/bluetooth/qdeclarativebluetoothdiscoverymodel.cpp @@ -403,6 +403,7 @@ void QDeclarativeBluetoothDiscoveryModel::setRunning(bool running) } d->m_serviceAgent->setRemoteAddress(QBluetoothAddress(d->m_remoteAddress)); + d->m_serviceAgent->clear(); if (!d->m_uuid.isEmpty()) d->m_serviceAgent->setUuidFilter(QBluetoothUuid(d->m_uuid)); -- cgit v1.2.3