Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Backtrace open qt ui files #36
For release 0.24.10 I create some qt designer ui files.
------ small program to load the ui files:
----- backtrace click on cancel:
In case I comment out to destroy the GUI I receive:
The same program runs fine in 0.24.10 with the same Release of QT and python.
The problem is not related to the way the dialog is produced. In fact, the root cause is the "destroy" call. "destroy" will delete the Qt object and is equivalent to C++ "delete". But while this is done, the event handler is still active and destroying the object in that phase basically means digging your own grave. The effect is undefined and it's very difficult to predict when this will work. 0.25 has been significantly enhanced over 0.24.10 in that area. That will explain the effect.
I can try to harden the code against such behaviour, but the solution preferred by Qt is to use "deleteLater":
"deleteLater" defers the delete until it's safe to do so.
Another solution is to configure the Dialog as "deleteOnClose" (setting