Fix leaky QT widgets #108
Merged
Fix leaky QT widgets #108
+97
−62
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 15, 2023
Closed
1123512 to
92186d1
Compare
|
I've managed to fix them all, apart from |
Merged
215e185 to
221e479
Compare
Fix parent typing Fix QWidget import
fda8647 to
1a7324d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables a check for leaky QT widgets. This is done in
conftest.pyby setting the "NAPARI_STRICT_QT" environment variable during the tests.To make the the widgets watertight I had to do two things:
parentkeyword argument to make sure all widgets have a parent widget. This is important, because parent widgets will pro-actively close any of their children when they themselves are closed.magicgui. Previously there was a circular reference that prevented the widget and one of the menusmagicguicreated from being cleaned up. I think the new code is a bit more readable if anything, and makes it clear where callbacks are between the combo boxes and the graph drawing. To test this runexamples/features_scatter.pyand have a play around with the widget.Fixes #109