Export overwite files handling

Nick

Exporing with latest v4.0.58 beta (update from v3)

It seems that the handling of saving export image is changed. In the old version, I remember it will remove (or simply overwite?) old export files before saving the new one. Now every time I run my batch export script, there will be more duplicated texture in the export folder because it try to avoid overwriting old file (but not the 1st one strangely) when there are multiple image to be export.

Btw, I would suggest the subsequent texture file name to use a more robust naming to avoid colliding with user defined skeleton name.

e.g.
I have BattleScene1, BattleScene2, BattleScene3. Each of them will export

BattleScene1.png
BattleScene2.png
BattleScene3.png

However, if a project export multiple images. BattleScene1 will export:

BattleScene1.png
BattleScene2.png  // same name from BattleScene2 export

which will have a name collision with next one.

Thus, I would suggestion a less likely used format for the auto naming.

e.g.

BattleScene1.png
BattleScene1__2.png
BattleScene1__3.png

BattleScene2.png
BattleScene2__2.png
BattleScene3__3.png

This way, you can safely remove old exports without worry about erasing exports from other similar named projects.

Nate

You're right, this was an accidental change. We'll fix it in 4.0.59-beta.

Spine adds a dash if the name already ends with a number. This doesn't match the behavior for image export, which uses underscore. We'll revise it to match, so you'll get name, name_2, name_3, etc.