View Single Post
Old 06-11-2011, 05:15 PM   #37
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,447
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I did that on purpose. The semantics of FunctionDispatcher are that the signal will be run in the thread that created the instance, thus the thread active in __init__. If the calling thread is the same as the creating thread, then the signal will never be received because the thread will be the same. There is no rule that the instantiating thread is the GUI thread.
chaley is offline   Reply With Quote