fixed: sprite user data positioned right after "Palette Chunk (0x2019)" leads to error while parsing aseprite file #26
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
…)" leads to error while parsing aseprite file See point 3. under https://github.com/aseprite/aseprite/blob/v1.3.8/docs/ase-file-specs.md#user-data-chunk-0x2020 for reference. Until now only the two older palette chunks ("Old palette chunk (0x0004)", "Old palette chunk (0x0011)") showed the correct behaviour. I don't know in what exact circumstances aseprite decides to use what palette chunk type, but I apparently have a mixture of these in my files, which is how I noticed.
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.
See point 3. under https://github.com/aseprite/aseprite/blob/v1.3.8/docs/ase-file-specs.md#user-data-chunk-0x2020 for reference.
Until now only the two older palette chunks ("Old palette chunk (0x0004)", "Old palette chunk (0x0011)") showed the correct behaviour.
I don't know in what exact circumstances aseprite decides to use what palette chunk type, but I apparently have a mixture of these in my files, which is how I noticed.
So to clarify: The following chunk orders parsed just fine:
The following chunk order failed parsing but parses now fine with this pull request: