Qt signals (QueuedConnection and DirectConnection)

by

You won’t see much of a difference unless you’re working with objects having different thread affinities. Let’s say you have QObjects A and B and they’re both attached to different threads. A has a signal called somethingChanged() and B has a slot called handleChange().

If you use a direct connection 

connect( A, SIGNAL(somethingChanged()), B, SLOT(handleChange()), Qt::DirectConnection );

the method handleChange() will actually run in the A‘s thread. Basically, it’s as if emitting the signal calls the slot method “directly”. If B::handleChange() isn’t thread-safe, this can cause some (difficult to locate) bugs. At the very least, you’re missing out on the benefits of the extra thread.

If you change the connection method to Qt::QueuedConnection (or, in this case, let Qt decide which method to use), things get more interesting. Assuming B‘s thread is running an event loop, emitting the signal will post an event to B‘s event loop. The event loop queues the event, and eventually invokes the slot method whenever control returns to it (it being the event loop). This makes it pretty easy to deal with communication between/among threads in Qt (again, assuming your threads are running their own local event loops). You don’t have to worry about locks, etc. because the event loop serializes the slot invocations.

Note: If you don’t know how to change a QObject’s thread affinity, look into QObject::moveToThread. That should get you started.

Edit

I should clarify my opening sentence. It does make a difference if you specify a queued connection – even for two objects on the same thread. The event is still posted to the thread’s event loop. So, the method call is still asynchronous, meaning it can be delayed in unpredictable ways (depending on any other events the loop may need to process). However, if you don’t specify a connection method, the direct method is automatically used for connections between objects on the same thread (at least it is in Qt 4.8).

More Related Contents:

  1. How to Compress Slot Calls When Using Queued Connection in Qt?
  2. QtCore.QObject.connect in a loop only affects the last instance
  3. Declare abstract signal in interface class
  4. How to leverage Qt to make a QObject method thread-safe?
  5. How to emit cross-thread signal in Qt?
  6. C++ Qt signal and slot not firing
  7. Starting QTimer In A QThread
  8. How to safely destruct a QThread?
  9. Why QFile(“./test”) work though [Class QFile] has no QFile(char* s) constructor
  10. Connecting overloaded signals and slots in Qt 5
  11. How to use the Qt’s PIMPL idiom?
  12. the procedure entry point __gxx_personality_v0 could not be located
  13. Qt5 Static Build yields Failed to load platform plugin “windows”
  14. How to deploy a Qt application on Windows?
  15. How to avoid Qt app.exec() blocking main thread
  16. undefined reference to template function [duplicate]
  17. How to change string into QString?
  18. Make QWidget transparent
  19. How do I create a Window in different QT threads?
  20. GIF animation in Qt
  21. How to append text to QPlainTextEdit without adding newline, and keep scroll at the bottom?
  22. QPSQL driver not loaded Qt
  23. qt thread with movetothread
  24. Changing locale in Qt
  25. Qt – remove all widgets from layout?
  26. QScrollArea with dynamically changing contents
  27. Using emit vs calling a signal as if it’s a regular function in Qt
  28. Convert std::string to QString
  29. How to create/read/write JSON files in Qt5
  30. Error: C2228: left of ” must have class/struct/union

Leave a Comment