Document object.properties does not store/load for non-aseprite file formats - #171
Open
Arecher wants to merge 1 commit into
Open
Conversation
…mats - Added note that setting a value in object.properties requires the sprite to be saved. - Added note that values in object.properties will not be stored on-disk for file formats such as `.png` or `.gif`. - Adjusted wording slightly in the introduction for Properties
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
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.
.pngor.gif.Ran into setting the properties and forgetting to save the sprite a few too many times, so I added it to the documentation. I similarly ran into an issue where setting
app.sprite.propertieson a.pngfile lost the data after one or two reloads, which I was extremely confused by until I realised it's a .png, and there likely is no way for this data to be stored on-disk. It worked fine for.asepritefiles.Do let me know if that assumption is wrong, and setting properties on a
.pngfile should store them on-disk and keep them on subsequent reloads, in which case I'll adjust the documentation and open a bug report for that instead!