I’m slightly confused by "runs within a QApplication thread process". Since there can only be a single QApplication, I’m guessing you either mean your GUI class manages its own worker thread(s), or your GUI class is *written* as a QThread subclass, which is then started by a call in Nuke and does all of its own bookkeeping.
Can you clarify the structure of your UI class and its use in Nuke a little? -Nathan From: Jordan O Sent: Wednesday, August 14, 2013 4:00 PM To: Nuke Python discussion Subject: [Nuke-python] Qt thread prevents nuke process from closing? Hey fellow TDs, I've got a recurrent issue that I can't seem to get around at our studio. I've built a Qt based render submitter for our artists using PySide. The submitter runs within a QApplication thread process. However when the submitter QApplication is closed and finished, I've noticed that Nuke's process will hang around indefinitely in memory (even if I close Nuke by clicking the "X" in windows as you normally would). Any ideas to make sure the Qt thread closes properly? I've even tried running del() on it. cheers, Jordan -------------------------------------------------------------------------------- _______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
