BUG: Bug with multi-view screen capture
See original GitHub issueSee this example that uses hemi='split', all captured PyVista images are duplicated:
Moreover, once brain.close() is called, it should make sure no figures are generated (as they have been closed for that snippet). Compare the above to what used to be produced with mayavi produced (one pair of images rather than four pairs):
cc @GuillaumeFavelier can you look into it?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Having some problem with s-pen and screen capture tracing... | XDA ...
This seems to happen mostly if I am tracing a smaller image. Am I doing something wrong or is this just a bug?...
Read more >Multi View Update Screen Rotation Bug Confirmed.
Hey All. This new firmware has introduced a screen rotation bug to our Note 2's. Basically the screen will fail to rotate from...
Read more >Bug Report - Monitor Capture bug with multi-monitor setup.
I have found somewhat of a work-around. I can fix the problem by enabling "Use point filtering" in the properties of the monitor...
Read more >Triple monitor bug
Can you post a screenshot of the multiview widget with your settings? I am curious what's going on here. Marcel Offermans, Mar 21,...
Read more >The Screen Capture Module
Shows the Capture Rectangle which can be dragged to the desired position. The size of the captured part of the screen equals the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@GuillaumeFavelier it would be nice not to have our docs have this problem when they go to
stable. So I think we either need this for 0.20, or we temporarily revert to using Mayavi to build docs during release…+1 for this @larsoner, I’ll open the PR