WIP: Fix some animation confusion #6421
Merged
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 fixes #6416.
It refactors and expands checking for the 'tight' figure bounding boxes that break piping image data to animation writers. First ,refactor things so that the writers can specify whether they handle changing figure sizes. By default
MovieWriter
(i.e. pipe-based writers) sets the flag toFalse
, whileMovieFileWriter
sets it toTrue
; this seems to work appropriately for all of the various writers (on OSX at least, but I don't think this is a platform issue). It also adds handling of the'savefig.bbox'
rcParam.The issue of what to do about being given a
MovieWriter
instance and kwargs for creating one remains TBD.