- Düzenlendi
Unexpected drity state
After saving the project, doing the following will mark the project dirty again:
- switch from Animation mode to Setup mode
- switching active animation
- exporting (occasional)
When no editing action is performed, will it be better if treat it as clean?
It seems like no that simple.
Sometime when switched animation and title bar show the dirty aster, the dirty state will get erased after getting back to Edit mode.
Changing the active animation changes the project and can be undone, so dirtying the project is correct.
Exporting can change paths and export settings that are stored in the project. This cannot be undone, but dirties the project so you know you need to save if you want to keep those settings. Previously we did not dirty the project and users were confused why their export settings were persisted only sometimes.
There can be scenarios where Spine has queued up undo commands that will later be purged. This is relatively rare and shouldn't cause any problems.