mirror of
https://github.com/subsurface/subsurface.git
synced 2025-02-19 22:16:15 +00:00
Ensure all found BLE services are tracked
If a device has more than one service the order of service discovery determined the selection of the service that we intend to interact with. This assumption is not accurate and is even platform dependent. Thinking ahead, it is likely that some devices may require us to keep track and interact with multiple services at the time. The new logic still suffers from the fact that there is no way to select the correct service for interaction. This will require higher level stack changes. Signed-off-by: Alex Blasche <alexander.blasche@qt.io> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
81dabe5ace
commit
57753321b0
2 changed files with 26 additions and 9 deletions
|
|
@ -2,6 +2,7 @@
|
|||
#ifndef QT_BLE_H
|
||||
#define QT_BLE_H
|
||||
|
||||
#include <QVector>
|
||||
#include <QLowEnergyController>
|
||||
#include <QEventLoop>
|
||||
|
||||
|
|
@ -14,7 +15,10 @@ public:
|
|||
~BLEObject();
|
||||
dc_status_t write(const void* data, size_t size, size_t *actual);
|
||||
dc_status_t read(void* data, size_t size, size_t *actual);
|
||||
QLowEnergyService *service;
|
||||
|
||||
//TODO: need better mode of selecting the desired service than below
|
||||
inline QLowEnergyService *preferredService()
|
||||
{ return services.isEmpty() ? nullptr : services[0]; }
|
||||
|
||||
public slots:
|
||||
void addService(const QBluetoothUuid &newService);
|
||||
|
|
@ -23,7 +27,9 @@ public slots:
|
|||
void writeCompleted(const QLowEnergyDescriptor &d, const QByteArray &value);
|
||||
|
||||
private:
|
||||
QLowEnergyController *controller;
|
||||
QVector<QLowEnergyService *> services;
|
||||
|
||||
QLowEnergyController *controller = nullptr;
|
||||
QList<QByteArray> receivedPackets;
|
||||
QEventLoop waitForPacket;
|
||||
};
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue