Skip to content

Document object.properties does not store/load for non-aseprite file formats - #171

Open
Arecher wants to merge 1 commit into
aseprite:mainfrom
Arecher:document-object-properties-only-saved-for-aseprite-files
Open

Document object.properties does not store/load for non-aseprite file formats#171
Arecher wants to merge 1 commit into
aseprite:mainfrom
Arecher:document-object-properties-only-saved-for-aseprite-files

Conversation

@Arecher

@Arecher Arecher commented Aug 19, 2026

Copy link
Copy Markdown
Contributor
  • 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

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.properties on a .png file 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 .aseprite files.

Do let me know if that assumption is wrong, and setting properties on a .png file 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!

…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant