QTcpSocket, execution halts why and what does it mean?

[SPlatten]

@KroMignon , do you mean isn't ?

Links:

https://doc.qt.io/qt-5/qabstractsocket.html#waitForConnected
https://www.bogotobogo.com/Qt/Qt5_QTcpSocket.php

There are many more.

[jsulm]

@SPlatten I don't see any event loop blocking loops in the links you posted. Your "while( mblnRun == true )" blocks the event loop. If you want to use Qt properly don't block the event loop - one of the most basic rules when using event driven frameworks.

[SPlatten]

@jsulm , thank you, can you please help me with an example?

[KroMignon]

@SPlatten said in QTcpSocket, execution halts why and what does it mean?:

can you please help me with an example?

Yes, but an example for doing what exactly?

[SPlatten]

@KroMignon , the examples I've found on QThread do not include how to NOT block the event loop, so an example on what to do in the thread so it doesn't block the event loop.

I've just added:

        QCoreApplication::processEvents();

To the thread loops, is this enough?

[Pl45m4]

@SPlatten

In general you can say that

• for(;;){}
• while(1)
• while(true) <- this is what you are doing basically

are pure evil, when used together with Qt GUI Framework. There might be some exceptions (esp. plain C++ code) but it's not safe to use it, when having signals&slots + events in use.

In your linked example this

if (socket->waitForConnected(1000))

for example, wont block the event loop forever, if this is what you were thinking.

[SPlatten]

@Pl45m4, I wasn't trying to block the event loop.

[KroMignon]

@SPlatten said in QTcpSocket, execution halts why and what does it mean?:

To the thread loops, is this enough?

I am not sure, is clsMsgSender a QThread or a QObject?

@SPlatten I will try to share with you how I use QTcpSocket.

First, there is no need to create a thread for that, the easiest implementation is (for me):

// supposing mSocket is a member of the current class
mSocket = new QTcpSocket();

// remove TCP delay
mSocket->setSocketOption(QAbstractSocket::LowDelayOption, 1);

QObject::connect(mSocket, &QAbstractSocket::connected,
                 [this]()
                 {
                    qDebug() << "Connected with" << mSocket->peerPort();
                    // Do stuff here                  
                 });
QObject::connect(mSocket, &QAbstractSocket::disconnected,
                 [this]()
                 {
                    qDebug() << "Disconnected from" << mSocket->peerPort();
                    mSocket->delateLater();
                    mSocket = nullptr;
                 });
QObject::connect(mSocket, &QIODevice::bytesWritten,
                 [this](qint64 bytes)
                 {
                    qDebug() << bytes << "send to " << mSocket->peerPort();
                    // do stuff (add next data?)
                 });
                 
mSocket->connectToHost(remoteIp, tcpPort);
QObject::connect(mSocket, &QIODevice::readyRead, [this](){
    auto buffer = mSocket->readAll();
    qDebug() << "receiving" << buffer.size() << "bytes from" << mSocket->peerPort();
    // do stuff with data
});

[Pl45m4]

@SPlatten said in QTcpSocket, execution halts why and what does it mean?:

the examples I've found on QThread do not include how to NOT block the event loop

Here, this wont block:

• https://www.bogotobogo.com/Qt/Qt5_QTcpSocket.php (your 2nd linked example)

This guy (https://stackoverflow.com/questions/37167927/proper-way-to-run-managable-background-thread-with-qthread) has made a similar mistake.
You want to connect once and then let the event loop and your signals do the rest.

[Christian Ehrlicher]

Funny - this discussion was already done more than 3 months ago already: https://forum.qt.io/topic/120700/receiving-data-from-qtcpsocket/30

[SPlatten]

@Christian-Ehrlicher , is it any surprise I'm confused, in that thread you pointed me to the Fortune client and server examples, which I have been following then there is conflicting advice that comes back form this forum when I implement a solution that I'm having problems with.

Add to this the what appears to be flaky Qt Creator with updates that seem to send me backwards. I feel I'm loosing the plot.

[Christian Ehrlicher]

The old thread told you to use signals and slots and not the waitFor functions and now we're at the exactly same place.

[SPlatten]

@Christian-Ehrlicher , well obviously I have mental memory issues.

[SPlatten]

@Christian-Ehrlicher , the examples that ship with Qt 5.15.2 include:

blockingfortuneclient
threadedfortuneserver

On looking at both, these are the sources I used to base my work on. My server is slightly different in that the clients are intended to stay connected after establishing a connection.

I will compare the client source with my own.

[Christian Ehrlicher]

From my pov you don't need threads at all but this is not what you want to hear for whatever reason - you rather work on simple stuff like a QTcpSocket for months.

[SPlatten]

@Christian-Ehrlicher , one day I will be ready to share what I'm working on, which isn't now.

[KroMignon]

@SPlatten said in QTcpSocket, execution halts why and what does it mean?:

one day I will be ready to share what I'm working on, which isn't now.

This sentence sounds strange to me.

I think you misunderstanding some comments/replies you received here.
My personal goal is to help other developers to solve problem they have will creating software with Qt, like I received help from other to solve/understand errors in my software.

On the other side, this also helps me to get a better overview of Qt Framework and continue to learn.

[SPlatten]

@KroMignon , sorry, some of the comments, not yours I find a little offensive.

[Pl45m4]

@KroMignon said in QTcpSocket, execution halts why and what does it mean?:

My personal goal is to help other developers to solve problem they have will creating software with Qt, like I received help from other to solve/understand errors in my software.
On the other side, this also helps me to get a better overview of Qt Framework and continue to learn.

This is exactly why I'm here :D