Can not open file from V 2.2.0 with V 2.1.1 with Designer

[TroKhon]

When trying to open a newly created - by V 2.2.0 1881  beta - file with Designer V 2.1.1 in afdesign format, I get the message, that it is not possible due to "containing features of a newer affinity version." Well, I think we should be able to open every 2.x file with every 2.x version - or have a conversion function...

[fde101]

This is normal.  It has only very rarely if ever been possible to open files from a newer version of the Affinity software with an older version.

 

This is also explicitly called out on the page where you can sign up for the betas:

Quote

Please also consider that documents saved in the beta versions may not be backward compatible with the currently released version.

https://affinity.serif.com/en-us/affinity-beta-program/

[TroKhon]

Yes, I am aware of that statement, but did not take it as final - my fault, and not a show stopper for me.

Will the final version be backwards compatible ? Since the statement only relates to "beta versions".... And "newer version" is for me not from 2.1 to 2.2 - from 1.x to 2.x it would be ok - and a converter function to exchange with someone who did not have the newest version would anyway be good. But again, I am would like this only for the final version, not for beta. Well, wishfull thinking....

[Return]

3 minutes ago, TroKhon said:

Will the final version be backwards compatible ?

No.

[walt.farrell]

8 minutes ago, TroKhon said:

Will the final version be backwards compatible ?

The naming of releases is of the form:

• Version, e.g., 1 or 2
• Release: e.g., 1.9, 1.10, 2.0, 2.1, 2.2
• Modification: e.g., 1.10.6, 2.0.4, 2.1.1, 2.2.0
• Build: e.g., 2.2.0.1881

The Version and Release numbers determine the file compatibility. When either of them changes, the file is incompatible with applications that have smaller Version or Release numbers.

The Modification and Build numbers do not affect file compatibility.

Thus, 1.8 could not open 1.9 files, 2.0 could not open 2.1 files, and 2.1 will not be able to open 2.2 files. But 2.0.3 could open 2.0.4 files, and 2.1.0 could open 2.1.1 files.

[TroKhon]

Ah - that makes the numbering much clearer. OK, I have to take it granted. But the Release version as compatibility determinator is a little surprise to me - but anyway, now I know what to expect. Thank you for this explanation.

Edited July 9, 2023 by TroKhon

[walt.farrell]

You're welcome.

[Pšenda]

On 7/9/2023 at 1:12 PM, walt.farrell said:

The naming of releases is of the form:

• Version, e.g., 1 or 2
• Release: e.g., 1.9, 1.10, 2.0, 2.1, 2.2
• Modification: e.g., 1.10.6, 2.0.4, 2.1.1, 2.2.0
• Build: e.g., 2.2.0.1881

Is this some kind of "official" division of the version items description? There are more ways to understand individual parts, for example:

 

Edited July 10, 2023 by Pšenda

[walt.farrell]

17 minutes ago, Pšenda said:

Is this some kind of "official" breakdown of the version items description? There are more ways to understand individual parts, for example:

It's the way I think of it. 

However you describe it, compatibility is determined by the first never and the number after the first period.

[Old Bruce]

16 hours ago, Pšenda said:

Is this some kind of "official" breakdown of the version items description? 

It is a convention.

[Pšenda]

Just now, Old Bruce said:

It is a convention.

walt's suggested division of version items is definitely not a "convention". There can be a lot of conventions - each manufacturer can break it down according to their needs and ideas, but the standard is usually Major and Minor versions for the first two items.
https://en.m.wikipedia.org/wiki/Software_versioning