FILE NAMING SUGGESTION DROPS PARTS OF FILE NAME

[OWEUX]

Hello Everyone,

 

I understand different people and environments have various theories and experiences guiding how and why they name files the way we do. Reasons aside, we are currently working on a project in which we regularly save our work and, on each 'meaningful' save, we add a version number. For example:

The 'format' we are using is [PROJECT_NAME]-[NEED_BY_DATE]-v[VERSION_NUMBER].[FILE_EXTENSION]

Example: "advert-2019-04-05-v0.6" and affinity adds its extension so that it becomes: advert-2019-04-05-v0.6.afdesign

Each time we use "SAVE AS" affinity DESIGNER and PHOTO will drop the minor version part of the filename. Using the example above, next time we press "SAVE AS" the program suggests "advert-2019-04-05-v0.afdesign". This seems also only happen when you open a file on their native file format. So if you open a DESIGNER file on PHOTO on first save the suggested name is OK but subsequent "SAVE AS" will start dropping characters.

I figure it is a REGEX issue but it is very annoying and can leads to some work being lost if someone inadvertently overwrites work because of a bad filename 'suggestion'.

Thank you for taking the time to read!

[woefi]

I tried to replicate this behaviour, as I also think this is very important.

As I just see – you are using the windows version.

If someone from the team reviews this, I can tell you: I'm on a mac and here this does NOT happen in any affinity-app (beta or regular).

[walt.farrell]

Welcome to the Serif Affinity forums, @OWEUX.

Interesting discovery. I can confirm that 1.6.5.135 works that way for me, too, on Windows. However, beta 1.7.0.284 works correctly, so Serif seems to have fixed that problem already in the beta version.