Copy text frame from 2.2 to 2.1

[MikeTO]

This isn't important but I noticed I can no longer copy a text frame from 2.2 to 2.1, it comes through as a group of art text objects, one per line of text.

We can copy text frames from 2.1 to 1.10 and I think in the 2.1 beta cycle we could copy text frames from 2.1 to 2.0. Perhaps this change was necessary due to some change in 2.2 but I'm asking in case it was an oversight.

Thanks

Edited August 6, 2023 by MikeTO
clarified

[Old Bruce]

1 hour ago, MikeTO said:

This isn't important but I noticed I can no longer copy a text frame from 2.2 to 2.1, it comes through as a group of art text objects, one per line of text.

 

I have to disagree about "not important", I would think it is quite important. 

I have to dash out for some time but I will try to play about with this bug. Happening here on Mac OS 12.6

[Done]

.

[MikeTO]

Thanks for confirming this

[Gabe]

We don't support backwards compatibility, so this is expected. 

[joe_l]

27 minutes ago, Gabe said:

We don't support backwards compatibility, so this is expected. 

Pardon? A textframe cannot be copied? Is there any major difference between textframes in 2.1 und 2.2 I missed? I can understand, that from 2.x to 1.x is no compatibility, but between subversions? Why do not simply "flag" elements as not compatible and make them invisible when you open 2.2 in 2.1? Of course I am no software engineer, so I cannot figure out consequences from this.

[Done]

.

[Gabe]

22 minutes ago, joe_l said:

Pardon? A textframe cannot be copied? Is there any major difference between textframes in 2.1 und 2.2 I missed? I can understand, that from 2.x to 1.x is no compatibility, but between subversions? Why do not simply "flag" elements as not compatible and make them invisible when you open 2.2 in 2.1? Of course I am no software engineer, so I cannot figure out consequences from this.

Yes. Due to serialisation. Some things may work, some may not. No different to having the "The file includes features from a later version of Affinity." error. In this case, it just falls back to PDF. 

[walt.farrell]

9 hours ago, Gabe said:

Yes. Due to serialisation. Some things may work, some may not. No different to having the "The file includes features from a later version of Affinity." error. In this case, it just falls back to PDF. 

Is it also expected that Artistic Text won't copy accurately between 2.2 and 2.1?

I find that trying to copy Frame Text gives the reported issue (multiple Artistic Text objects in 2.1) but additionally the font size is changed from 12pt to 2.88pt.

And when I try it with Artistic Text, the same happens. I get an Artistic Text object in 2.1, but the font size has changed from 12pt to 2.88pt. As that result is 24% (2.88/12), it feels like something is happening that is mis-handling a conversion between DPI (both documents are 300 DPI) and Points, since 72/300 is also 24%.

[Gabe]

That's a different issue, unrelated to copying from 2.2 into 2.1. PDF data from clipboard is incorrectly treated as being 72DPI, and therefore being scaled up/down. 

[Hangman]

16 hours ago, walt.farrell said:

I find that trying to copy Frame Text gives the reported issue (multiple Artistic Text objects in 2.1) but additionally the font size is changed from 12pt to 2.88pt.

And when I try it with Artistic Text, the same happens. I get an Artistic Text object in 2.1, but the font size has changed from 12pt to 2.88pt. As that result is 24% (2.88/12), it feels like something is happening that is mis-handling a conversion between DPI (both documents are 300 DPI) and Points, since 72/300 is also 24%.

I'm assuming this is Windows specific as it's not happening on macOS, yes, the pasted text appears as Artistic text when pasted between 2.2 and 2.1 but both frame and artistic text maintain their point size when pasted...