Qt 6.11 is out! See what's new in the release
blog
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?
@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 theQApplicationwas 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::DirectConnectionandQt::QueuedConnection) in most cases.