Please store the export path separately!

Martin2

The absolute path to the exported folder is stored in the spine file itself, making it difficult to work with in git.

As soon as someone on the team exports the file to a different absolute path it shows up as modified in git, even if nothing was actually changed. And every person who works with the files have to change the export path between each commit, because Spine doesn't remember it locally.

I believe the problem stems from this issue: https://esotericsoftware.com/forum/d/910-export-directory-not-stored-in-project.

A better fix would be to associate each project with a local settings file that is stored separately, in the user's local app data folder.

Could you please fix this?

Misaki

Martin2 Thank you for your feedback! We are aware of this issue and have an issue ticket on our roadmap for future improvement: EsotericSoftware/spine-editor515
I have added a link to this thread as a comment. You can subscribe to the issue ticket to receive additional notifications of progress.

Nate

Storing the paths in user settings (as Martin2 requests) is slightly different than using relative paths (as requested in the issue). Some people rely on the last export path being in the project file and would benefit from the paths being relative. This would also solve the git problem, for some use cases. It would not solve two users wanting to export to different paths though.

Martin2

Nate Solving both would be ideal! 🙂

Harald

@Martin2 Please also note that this issue only applies when manually exporting your files every time, instead of automating your exports using the Spine Command Line Interface (CLI). Then you could commit a shared export script and also shared export settings .export.json files to git.

See this posting for example on CLI exports:
https://esotericsoftware.com/forum/d/15981-spine-unity-38-to-40-upgrade-guide/6