Important: Please read the Qt Code of Conduct -

Signal from QML to C++ and threads

  • Hey,

    I have a login screen in QML. When the user clicks "Login" a signal is emitted, which is processed in a C++ object. The C++ objects does the login, which is a time consuming operation.

    Now my question: Should the C++ object start a separate thread for this? If the signal-processing function (the slot) takes time, will it block the UI (or other stuff) and is it already in a separate thread?


  • If UI is first thread and signal-processing function is second thread, then second thread should not block the first thread.

    But everything depends on the implementation of

  • That makes sense.

    But is the implementation consistent across platforms and Qt versions?

Log in to reply