On 18/09/15 12:40, "Blasche Alexander"
wrote:
>
>
>From: Knoll Lars
>
>
>>void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
>>QBluetooth::SecurityFlags preferredSecurityFlags() const;
>
>It would be a behavior change. Prior to this API we use
From: Knoll Lars
>void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
>QBluetooth::SecurityFlags preferredSecurityFlags() const;
It would be a behavior change. Prior to this API we used one default way to
connect. On all platforms this happ
Only new API is
void setPreferredSecurityFlags(QBluetooth::SecurityFlags flags);
QBluetooth::SecurityFlags preferredSecurityFlags() const;
API Looks good, but I’m wondering why the default on bluez is not Secure
as on the other platforms?
Cheers,
Lars
_
diff --git a/src/bluetooth/qbluetoothlocaldevice.h b/src/bluetooth/qbluetoothlocaldevice.h
index 4587bbf..40e143a 100644
--- a/src/bluetooth/qbluetoothlocaldevice.h
+++ b/src/bluetooth/qbluetoothlocaldevice.h
@@ -113,4 +113,8 @@ private:
QT_END_NAMESPACE
+Q_DECLARE_METATYPE(QBluetoothLocalDevi