<![CDATA[Modeless dialog]]>If I have understood the docs correctly a modeless dialog has its own event loop. Does that mean that it is effectively running in a separate thread? If so, should signals be connected as Qt::QueuedConnection?

]]>https://forum.qt.io/topic/163880/modeless-dialogRSS for NodeWed, 16 Sep 2026 03:40:11 GMTMon, 08 Dec 2025 12:04:14 GMT60<![CDATA[Reply to Modeless dialog on Wed, 10 Dec 2025 11:45:30 GMT]]>Understood. Thanks.

]]>https://forum.qt.io/post/834483https://forum.qt.io/post/834483Wed, 10 Dec 2025 11:45:30 GMT<![CDATA[Reply to Modeless dialog on Mon, 08 Dec 2025 14:23:13 GMT]]>@Buller said in Modeless dialog:

Does that mean that it is effectively running in a separate thread?

No.
Event loop != thread
The whole Qt GUI is single threaded only and Qt GUI elements must only be accessed from the "main" GUI thread... the thread of your program where the QApplication was created.

If so, should signals be connected as Qt::QueuedConnection?

No, you can omit the fifth argument anyway since Qt will pick the right one for you (between Qt::DirectConnection and Qt::QueuedConnection) in most cases.

]]>https://forum.qt.io/post/834401https://forum.qt.io/post/834401Mon, 08 Dec 2025 14:23:13 GMT