Ballshamin Posted April 7 Posted April 7 Greetings... I have three Affinity tools: Publisher, Designer and Photo and some days ago I updated from a version of Designer to the next and created a graphic. Then I tried to insert the graphic in Publisher —which I had not updated— and when I try it, a message appears saying that the version of the file is not compatible and does not allow me to insert it. It seems logical that in case of important changes in the application, the program warns of incompatibilities, but it does not seem logical between versions such as 2.5.6 and 2.5.7 —I don't remember exactly between which versions the problem has appeared, so I mentioned these as an example—. Is there no standard file format that admits extensions? Wouldn't it be more logical to notify the user, but at least open the file with the supported features? There're not so many changes between two successive versions of the products. This policy makes files unusable between applications if they are not exactly in the same version. Quote
Staff MEB Posted April 7 Staff Posted April 7 HI @Ballshamin, Update the other two apps to the latest version and you should be able to open the file you created in the updated Designer app. There's no backwards compatibility, so new/updated versions of our file format may not open in previous/older versions. Quote A Guide to Learning Affinity Software
walt.farrell Posted April 7 Posted April 7 If you update from 2.5.6 to 2.5.7 (change in the number after the second ".") the file should remain compatible. If you update from 2.5.something to 2.6.something (change in the number after the first ".") then the files generally will not be backward compatible. And as MEB has mentioned, you should update all 3 apps at the same time. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Meliora spero Posted April 7 Posted April 7 10 hours ago, Ballshamin said: Is there no standard file format that admits extensions? Wouldn't it be more logical to notify the user, but at least open the file with the supported features? There're not so many changes between two successive versions of the products. This policy makes files unusable between applications if they are not exactly in the same version. This is because Serif, in their wisdom, chose a primitive and fragile file format - one delightfully prone to corruption. Oh, granted, more intelligent and resilient formats have been publicly available since at least 1985 - well before Serif even existed - but apparently, they opted for something more fitting for the gaming industry than for professional design work. Serif were probably aiming for performance - and I must admit, when file corruption does happen, at least it’s impressively swift. Quote Serif, did you foolishly fill the usability specialist role you advertised internally? If so, be transparent with your customers. Continuing without proper UX expertise both insults and affects your entire customer base.
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.