Helper to create a new figure/axes in a qt-safe way #91
Conversation
This file contains 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
Tom-Willemsen
force-pushed
the
qt_create_axes
branch
from
2f37c8d to
108beef
Compare
Tom-Willemsen
force-pushed
the
qt_create_axes
branch
from
108beef to
4b2af43
Compare
rerpha
previously approved these changes
Dec 2, 2024
rerpha
approved these changes
Dec 2, 2024
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.
Fixes #92
Calling
plt.subplotsdirectly in a plan breaks, if the matplotlib backend isqt(e.g. if running a plan in a standalone shell).That's because it would try to interact with the Qt gui from the RunEngine's plan worker thread, which is invalid. Instead we need to force it to go through bluesky's matplotlib-qt integration infrastructure.
To review:
main)