readyread() signal doesn't emit after sendmessage() signal on pushbutton

SGaist

Hi,

Unless you get some answer from the server there's no reason for readyRead to be emitted.

fari35

@SGaist yes the client is sending the message to the server and the server is emitting the readyread() signal even if the client sends 10 messages to the server readyread() will be emitted until i press the send button and as soon as the sendmessage() signal is emitted readyread() signal doesn't emit after that

Christian Ehrlicher

I would guess it's a threading problem - don't use threads when you don't need them (and don't understand it's consequences). The first thing which shows me that you don't really understand what you're doing is that you're using Qt::DirectConnection - it's not needed in 99,99% of all usecases. Qt knows what connection type to use.
And since you're using thread I would guess that the QTcpSocket is not created in the htread from where you access it (either reading or writing, don't know your code) and therefore you kill the socket notification which exactly explains your findings.

ChrisW67

The code emits a sendmessage() signal from the MainWindow class. Nothing shown connects the signal to anything. It is entirely possible nothing is listening to it and therefore nothing happens.

The code has a sendmessage() function on a class called fthread. The function is not related to the signal in MainWindow. It's not clear whether you think it is or not.

fari35

@Christian-Ehrlicher I have attached my code in the question and I have created a QTcpSocket. The whole program is working fine until I press the send button and after that the readyread() and disconnected() signla doesn't emit.

fari35

@ChrisW67 I have attached the code for sendmessage() signal

mrjj

@fari35

Hi
Did you put a break point in each sendmessage and gotNewMesssage functions to make sure you did not
create a ping-pong situation where signals are kept firing?

fari35

@mrjj as soon as the signal is emitted it executes a slot and then returns and continue its execution. There is some problem in threading. Like I also checked after putting a sleep statement in readyread() signal in fthread.cpp file and it worked fine for like some time and after that it crashed and then didin't work

mrjj

@fari35

well put breakpoints on the slots and check they are called just once when you press the send button.

fari35

@mrjj Yes, I have checked right nnow the slots are only called once

JonB

@fari35
I have told you before to put qDebug() statements in. You are supposed to do more investigation yourself and report the exact problem rather than just keep throwing your whole code at the community for answer....

fari35

@JonB I didn't attch the whole code initially but after they asked for it , I've attached my whole code, but now I have cut it short. the problem I'm getting is that readyread() siggnal is not emitting after send button is pressed. Before pressing the send button it emits even if the client sends 10 messages it emits 10 times but as soon as the send button is pressed it stops emitting

Christian Ehrlicher

The code still does not show where the QTcpSocket is created - and when it's like I guess you implemented it, it's still created in the wrong thread. Please provide a minimal, compilable example!

fari35

@Christian-Ehrlicher here is the code for run() where QTcpSocket is created:

void fthread::run()
{


    tcpSocket = new QTcpSocket();

    if (!tcpSocket->setSocketDescriptor(socketDescriptor)) {
        emit error(tcpSocket->error());
        return;
    }

    connect(tcpSocket, SIGNAL(readyRead()), this, SLOT(readyRead()));

    connect(tcpSocket, SIGNAL(disconnected()), this, SLOT(disconnected()));

    exec();

}

Christian Ehrlicher

@fari35 said in readyread() signal doesn't emit after sendmessage() signal on pushbutton:

connect( this, SIGNAL(sendmessage(QString)),thread_obj, SLOT(sendmessage(QString)));

As I said - the function sendmessage(QString) is executed in the main thread. Please read the docs about QThread or don't use QThread at all when you don't know the basics. There is no reason to use threads at all...

fari35

@Christian-Ehrlicher Actually I need to make a multi threaded server for my project and I'm using Qt for that. I want to send the message to all the clients who have been assigned a separate thread, Can you please tell me how can I do that because I'm not getting it.

JonB

@fari35
What is it you need beyond the Threaded Fortune Server Example ? How much are you based on that?

fari35

@JonB In this example it's not shown how to send the message to the client if the signal is emitted from the main thread like here I'm making a UI for the server so I want to send the message to the client as soon as the send button is clicked, but I don't know how to do it. I'm not even getting help from anywhere.

Christian Ehrlicher

Again: if you want to use thread (for whatever reason, maybe just to show that you're a famous programmer...), make sure you understand what you're doing and read the documentation and examples:

"It is important to remember that a QThread instance lives in the old thread that instantiated it, not in the new thread that calls run(). This means that all of QThread's queued slots and invoked methods will execute in the old thread. Thus, a developer who wishes to invoke slots in the new thread must use the worker-object approach; new slots should not be implemented directly into a subclassed QThread."

JKSH

@fari35: To clarify the documentation quoted by @Christian-Ehrlicher's: Do not implement any slots in fthread. Instead, implement your slot in a separate QObject. Create that object together with tcpSocket.