reorganized Figure export stuff by kushalkolar · Pull Request #710 · fastplotlib/fastplotlib · GitHub
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
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.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.
Footer
You can’t perform that action at this time.
Adds a new method Figure.export_numpy().
Removes the FigureRecorder because that thing is hard to test and IMO kinda out of scope and a mess. Instead once we expose the "onedemand" render mode in fastplotlib which now exists in rendercanvs we can provide examples using Figure.export_numpy() to export frames as numpy arrays that can then be written to disk using the user's favorite video writer, such as opencv.
@apasarkar @FlynnOConnell
These examples currently don't work because we don't have "ondemand" mode in fastplotlib yet, documenting here for a future PR: