Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
5.14
-
None
Description
Hello,
I'm not sure if this is really an issue or if I just misuse/misunderstand the Qt bluetooth layer.
The use case is the following:
I have a BLE peripheral communicating with a BLE controller over two characteristics (one WRITE, one INDICATE).
When using Qt to write to the INDICATE characteristic on the peripheral side some data longer than the MTU, I split the buffer into several smaller buffers, and call repeatedly QLowEnergyService::writeCharacteristic()
The problem with this approach is that I have no way to know that the data were read by the central before writing the next buffer.
Doing the same thing on android, there is a callback onNotificationSent that can be used to know when the next buffer can be sent.
I'm attaching a patch I wrote to be notified, but I strongly doubt that this is the good approach.