From fa54696446eaed03c2b84ca3e3c0c81ef5d42bea Mon Sep 17 00:00:00 2001 From: Alex Blasche Date: Tue, 30 Aug 2016 15:43:32 +0200 Subject: Remove ambiguity when using QTimer::setInterval() pointer in example This is required because QTimer introduced a new overload for setInterval(). Change-Id: I7dbf2eb9b424132439fc420b84584d2f55498c3c Reviewed-by: Simon Hausmann --- examples/serialbus/modbus/adueditor/modbustcpclient_p.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/examples/serialbus/modbus/adueditor/modbustcpclient_p.h b/examples/serialbus/modbus/adueditor/modbustcpclient_p.h index 50bcc04..0ec769a 100644 --- a/examples/serialbus/modbus/adueditor/modbustcpclient_p.h +++ b/examples/serialbus/modbus/adueditor/modbustcpclient_p.h @@ -85,7 +85,8 @@ public: m_responseTimeoutDuration }; m_transactionStore.insert(m_tId, element); - q->connect(q, &QModbusClient::timeoutChanged, element.timer.data(), &QTimer::setInterval); + q->connect(q, &QModbusClient::timeoutChanged, + element.timer.data(), QOverload::of(&QTimer::setInterval)); QObject::connect(element.timer.data(), &QTimer::timeout, [this, writeToSocket]() { if (!m_transactionStore.contains(m_tId)) return; -- cgit v1.2.3