OWEUX Posted April 2, 2019 Share Posted April 2, 2019 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! Quote Link to comment Share on other sites More sharing options...
woefi Posted April 2, 2019 Share Posted April 2, 2019 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). Quote Main machine: iMac 2019 (21,5-inch 4k, 6core), 64GB RAM, 1TB nvme + 2TB ssd, running on Mac OS 13; Display setup: 28" 5k Display (primary) + 21,5" iMac4k-Display for studio panels (secondary); Keyboard layout: german apple extended keyboard (aluminium); Link to comment Share on other sites More sharing options...
walt.farrell Posted April 2, 2019 Share Posted April 2, 2019 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. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.