<![CDATA[Unwanted Windows Command Prompt when using QSignalSpy::wait()]]>I'm using a QSignalSpy::wait() to wait for a specific reply during TCP communication. But by including testlib, the app always opens a command prompt on Windows. Is there any way to suppress that (I'm using qmake and coding on Debian btw)? Or can you suggest a workaround?

Currently, I'm emitting a custom signal upon receiving the reply I expect, which is connected to a QSignalSpy.

]]>https://forum.qt.io/topic/139423/unwanted-windows-command-prompt-when-using-qsignalspy-waitRSS for NodeSat, 31 Oct 2026 09:36:35 GMTMon, 19 Sep 2022 13:35:03 GMT60<![CDATA[Reply to Unwanted Windows Command Prompt when using QSignalSpy::wait() on Mon, 19 Sep 2022 13:38:34 GMT]]>@JKappes said in Unwanted Windows Command Prompt when using QSignalSpy::wait():

I'm using a QSignalSpy::wait() to wait for a specific reply during TCP communication

Why? QSignalSpy is meant to be used in tests. If you really have to wait (do you really have to?) then you should use a local event loop instead.

]]>https://forum.qt.io/post/729304https://forum.qt.io/post/729304Mon, 19 Sep 2022 13:38:34 GMT<![CDATA[Reply to Unwanted Windows Command Prompt when using QSignalSpy::wait() on Tue, 20 Sep 2022 06:53:40 GMT]]>@JKappes said in Unwanted Windows Command Prompt when using QSignalSpy::wait():

It's better for UX to wait

I disagree - you're blocking the UI, this can be frustrating for the user. But its you application.

]]>https://forum.qt.io/post/729388https://forum.qt.io/post/729388Tue, 20 Sep 2022 06:53:40 GMT<![CDATA[Reply to Unwanted Windows Command Prompt when using QSignalSpy::wait() on Mon, 19 Sep 2022 13:46:00 GMT]]>@jsulm That's just the first way I got it to work.
It's better for UX to wait, so I'll try an event loop. Thanks for the tip.

]]>https://forum.qt.io/post/729305https://forum.qt.io/post/729305Mon, 19 Sep 2022 13:46:00 GMT<![CDATA[Reply to Unwanted Windows Command Prompt when using QSignalSpy::wait() on Mon, 19 Sep 2022 13:38:34 GMT]]>@JKappes said in Unwanted Windows Command Prompt when using QSignalSpy::wait():

I'm using a QSignalSpy::wait() to wait for a specific reply during TCP communication

Why? QSignalSpy is meant to be used in tests. If you really have to wait (do you really have to?) then you should use a local event loop instead.

]]>https://forum.qt.io/post/729304https://forum.qt.io/post/729304Mon, 19 Sep 2022 13:38:34 GMT