<![CDATA[gotnewmessage() signal does not emit after sendmessage() signal]]>https://forum.qt.io/topic/122706/gotnewmessage-signal-does-not-emit-after-sendmessage-signalRSS for NodeSat, 25 Apr 2026 23:17:15 GMTThu, 14 Jan 2021 15:12:19 GMT60<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 19:16:11 GMT]]>Because there's no reason for that to happen. You just connected a signal to another signal.

Excuse me for being blunt but: your current code is a mess. Your architecture is wrong on several levels. You seem to want some kind of threaded server inside a GUI while also making it its own client but without any connection.

As I already suggested, if you really want to use threads (and you really don't at this stage), read the threaded fortune server example.

Keep things clearly separated. Have one server component, then build your GUI to use that component. Look for aggregation VS inheritance.

]]>https://forum.qt.io/post/637983https://forum.qt.io/post/637983Thu, 14 Jan 2021 19:16:11 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 18:59:29 GMT]]>@SGaist ohh I just figured out once sendmessage() signal is emitted from mainwindow class then the readyread() function is not executed in fthread class. But why is that so?

]]>https://forum.qt.io/post/637980https://forum.qt.io/post/637980Thu, 14 Jan 2021 18:59:29 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 18:29:27 GMT]]>That will be part of the problem at some point because it makes your code messy.

In any case, you have an issue with the socket creation as it's not done in the correct thread.

You should really clean your implementation. It will make your code easier to manage and debug.

]]>https://forum.qt.io/post/637975https://forum.qt.io/post/637975Thu, 14 Jan 2021 18:29:27 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 18:24:54 GMT]]>@SGaist Actually that's not the problem. The problem is that it is emitting gotnewmessage() signal until I don't click send button in mainwindow class to emit sendmessage() signal, but once sendmessage() signal is emmitted gotnewmessage() signal doesn't emit

]]>https://forum.qt.io/post/637973https://forum.qt.io/post/637973Thu, 14 Jan 2021 18:24:54 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 18:19:18 GMT]]>This is not how it works. Please check the threaded fortune server example if you really want to use threads.

In any case, the way you use multiple inheritance is wrong.

]]>https://forum.qt.io/post/637971https://forum.qt.io/post/637971Thu, 14 Jan 2021 18:19:18 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 18:10:32 GMT]]>@SGaist because I want to use the same object of fthread class in both the server and mainwindow class

]]>https://forum.qt.io/post/637970https://forum.qt.io/post/637970Thu, 14 Jan 2021 18:10:32 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 17:58:35 GMT]]>Hi,

@fari35 said in gotnewmessage() signal does not emit after sendmessage() signal:

class fserver : public QTcpServer,public threadobj

Why the double heritage ?

]]>https://forum.qt.io/post/637967https://forum.qt.io/post/637967Thu, 14 Jan 2021 17:58:35 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 17:42:55 GMT]]>@Christian-Ehrlicher ok I have corrected that. Can you please tell me why gotnewmessage() is not working after sendmessage() signal is emmited from windows class?

]]>https://forum.qt.io/post/637964https://forum.qt.io/post/637964Thu, 14 Jan 2021 17:42:55 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 17:36:48 GMT]]>I did not look what the code really does but tcpSocket is created in the wrong thread. You must create it inside run() so it's created in the new thread.

]]>https://forum.qt.io/post/637963https://forum.qt.io/post/637963Thu, 14 Jan 2021 17:36:48 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 17:09:42 GMT]]>@aha_1980 @kshegunov @Christian-Ehrlicher Do you have anyidea about this?

]]>https://forum.qt.io/post/637960https://forum.qt.io/post/637960Thu, 14 Jan 2021 17:09:42 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 17:01:00 GMT]]>@fari35
Too much for me, and I've done my bit. You should cut down the code to make it minimal and put qDebug() statements in to see what is/is not getting called.

As a separate matter, get rid of old-style SIGNAL/SLOT() macros and always use new style. You presently have a mixture.

]]>https://forum.qt.io/post/637957https://forum.qt.io/post/637957Thu, 14 Jan 2021 17:01:00 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 16:53:54 GMT]]>@JonB I have now attached my whole code in the question. Can you please tell me what is wrong here?

]]>https://forum.qt.io/post/637956https://forum.qt.io/post/637956Thu, 14 Jan 2021 16:53:54 GMT<![CDATA[Reply to gotnewmessage() signal does not emit after sendmessage() signal on Thu, 14 Jan 2021 15:24:09 GMT]]>@fari35
You're going to have show code for anyone to comment. In itself the fact that you changed how sendmessage() is sent/connected cannot affect something not being able to emit its own message.

Try to show just the relevant bare-bones. We probably don't need to see the send message side, but do we do need to see (a) confirmation that the thread's slot is called from the send message and (b) how the thread does its emit gotnewmessage() and (c) how that emitted signal is connected to the slot which should act on it. Put in qDebug()s to prove what's going on!

]]>https://forum.qt.io/post/637941https://forum.qt.io/post/637941Thu, 14 Jan 2021 15:24:09 GMT