Add serialization functions #140
Merged
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
I think it's enough for this PR at least, since saving to a file is very context-specific. But a lightweight implementation for demo purposes might not hurt. Anything beyond that may very well balloon out of the scope of what makes sense for an actual Toolkit feature, though. |
|
That's a good point, I'm going to merge this. |
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.
Adds 2 functions to GaeaGenerator:
serializereturns aPackedByteArraythat represents the currently generated grid.deserializetakes these bytes and sends them to the grid.Is this enough for serialization or should we also add functions to save for files? I feel like that should be left to the user, but if there's enough demand I'll add them.