Details
-
Suggestion
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
The Problem is, that Qt for Python really likes things done in its main thread and specific things in a QThread. It really does not like any regular Python threads to the point of using them in combination with Qt resulting in a segmentation fault.
Kivy, another UI Framework has a very simple solution to this Problem.
It has a @mainthread function decorator. That will queue up that call into the main threads event queue and then wait for that to be called and returned to the thread that called the function initially.
An example can be found here:
https://github.com/kivy/kivy/wiki/Working-with-Python-threads-inside-a-Kivy-application
Attachments
Issue Links
- relates to
-
PYSIDE-1238 Don't explicitely expose QApplication when extending a Qt/C++ application
- Reported