[Qt-interest] QApplication on separate thread...

[Jason H]

The non-Qt app is a process, the Qt app is a process. Processes are "fat" threads. The threads spawned by your Qt app are children of the Qt app, and all signal/slotting is done only in Qt threads. The process tree however will show that the non-Qt app is parent to the Qt app. The only behavior this implies is if the non-Qt app is killed, so is the Qt app.

If you want to have Qt talk to the non-Qt app, or vise-versa, then you need some communication mechanism to bridge the two.





________________________________
From: Eric Clark <eclark at ara.com>
To: "qt-interest at trolltech.com" <qt-interest at trolltech.com>
Sent: Tue, June 22, 2010 1:35:50 PM
Subject: [Qt-interest] QApplication on separate thread...

 
Hello All,
 
I have a non-Qt application that loads a Qt application. The
non-qt application would like to instantiate and start the Qt application on a
separate thread than the main thread in which it resides. I am getting some
errors associated with sending signals to objects on different threads. I was wondering
if anyone could tell me if it is possible to have a QApplication that resides
on a thread different than that of the main application? Or is it a requirement
that the QApplication reside on the application’s main thread?
 
Thank You in Advance!
Eric


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100622/5ee03e9f/attachment.html