summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArno Rehn <a.rehn@menlosystems.com>2022-09-02 15:20:43 +0200
committerArno Rehn <a.rehn@menlosystems.com>2022-09-02 15:29:02 +0200
commite97700b7ba5267592b25622d97e8faafd6872369 (patch)
treedfc3092767450158646e58e73cd1cb6b01c996e9
parent450056db1c9d65bccb75cec83be9535b918c30db (diff)
downloadqtwebchannel-e97700b7ba5267592b25622d97e8faafd6872369.tar.gz
Remove warnings about no transport being connected
No transport being connected is a usual situation for a QtWebChannel server. It just so happens when no client is connected. Printing warnings about no transports being connected just creates spam in the logs without any gain. Change-Id: Ia74918112a7012437a5b6f1ed97f1c4bbd557816 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
-rw-r--r--src/webchannel/qmetaobjectpublisher.cpp3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/webchannel/qmetaobjectpublisher.cpp b/src/webchannel/qmetaobjectpublisher.cpp
index 62d5319..d25bed0 100644
--- a/src/webchannel/qmetaobjectpublisher.cpp
+++ b/src/webchannel/qmetaobjectpublisher.cpp
@@ -1013,7 +1013,6 @@ void QMetaObjectPublisher::deleteWrappedObject(QObject *object) const
void QMetaObjectPublisher::broadcastMessage(const QJsonObject &message) const
{
if (webChannel->d_func()->transports.isEmpty()) {
- qWarning("QWebChannel is not connected to any transports, cannot send message: %s", QJsonDocument(message).toJson().constData());
return;
}
@@ -1025,8 +1024,6 @@ void QMetaObjectPublisher::broadcastMessage(const QJsonObject &message) const
void QMetaObjectPublisher::enqueueBroadcastMessage(const QJsonObject &message)
{
if (webChannel->d_func()->transports.isEmpty()) {
- qWarning("QWebChannel is not connected to any transports, cannot send message: %s",
- QJsonDocument(message).toJson().constData());
return;
}