View Single Post
Old 10-18-2019, 11:38 AM   #3
thiago.eec
Wizard
thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.
 
Posts: 1,217
Karma: 1419583
Join Date: Dec 2016
Location: Goiânia - Brazil
Device: iPad, Kindle Paperwhite, Kindle Oasis
Quote:
Originally Posted by kovidgoyal View Post
You should only use Qt objects on a single thread. There is a way to transfer objects from onethread to another, but I would not bother. Instead have your worker threads emit signals with data in some non Qt object form, like a python dit or whatever and have the main thread convert it into needed Qt objects.
Thanks a lot, Kovid.

That gave me the clue where to find the problem: I had a message showing in the status bar that was being set inside the thread. I moved it outside and everything is fine now!

thiago.eec is offline   Reply With Quote