diff options
| author | Andy Shaw <andy.shaw@qt.io> | 2019-02-05 00:29:14 +0100 |
|---|---|---|
| committer | Andy Shaw <andy.shaw@qt.io> | 2019-02-05 16:05:16 +0000 |
| commit | 005cef90c6e06ef419dcec8f4619402677470301 (patch) | |
| tree | d2c64445d3585b1fa74e53a3986aa02051fc0c80 | |
| parent | dafbd24e9fcf74bc946111e2bb1547fc3d44e90b (diff) | |
Fully qualify the parameter in QNearFieldManager::adapterStateChangedv5.13.0-alpha1
The signal parameter needs to be fully qualfied so that it can be
correctly matched when using the macros.
This can cause a breakage if an application was connecting using the
non fully qualified type, which can be the case if invokeMethod() or
similar is used. However the chances of this are incredibly slim, and
it is worth the risk to ensure normal connections will work correctly.
[ChangeLog][Important Behavior Changes][QtNFC][QNearFieldManager]
adapterStateChanged now has a fully qualified parameter -
QNearFieldManager::AdapterState. This can cause a problem if the
connection/method invocation was done with just AdapterState as
the parameter type, in which case these need to be changed to
use QNearFieldManager::AdapaterState instead.
Change-Id: I7311ff4cb15b67089ceb5917961ee979c9566f28
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
| -rw-r--r-- | src/nfc/qnearfieldmanager.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nfc/qnearfieldmanager.h b/src/nfc/qnearfieldmanager.h index 500b9631..22506e7e 100644 --- a/src/nfc/qnearfieldmanager.h +++ b/src/nfc/qnearfieldmanager.h @@ -99,7 +99,7 @@ public: bool unregisterNdefMessageHandler(int handlerId); Q_SIGNALS: - void adapterStateChanged(AdapterState state); + void adapterStateChanged(QNearFieldManager::AdapterState state); void targetDetected(QNearFieldTarget *target); void targetLost(QNearFieldTarget *target); |