-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix a few issues with Plotter.show #3889
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3889 +/- ##
==========================================
+ Coverage 94.16% 94.19% +0.02%
==========================================
Files 91 91
Lines 19586 19566 -20
==========================================
- Hits 18444 18431 -13
+ Misses 1142 1135 -7 |
There is a very odd image regression failure showing up here... hoping that #3891 resolves it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor changes, otherwise LGTM.
Since we're maintaining backwards compatibility as much as possible, I agree with the changes here and appreciate removing store_image
. It always felt like a hack.
Thanks! Merging after CI turns green and will sync #3897 |
Fix a few issues with
Plotter.show()
Resolves #1635, Resolves #3548, Resolves #2953, Resolves #1877, Resolves #1665, Resolves #1621
Some cleanups to improve the return values of
Plotter.show()
so that ifreturn_*
is set, the requested item will always be returned.Further, this removes the
store_image
property as the whole point oflast_image
was always to have an image after rendering. I probably need to deprecate this instead of outright removing...@akaszynski and @pyvista/developers, I would appreciate a thorough review on this one as changing up the
show()
method nearly always has unexpected consequences