Thanks for that. That’s sort of what I figured. A couple of thoughts, if thats ok:
1. This behaviour applies to edits made using other 3rd party apps too. They also get stripped. Being honest, I haven’t tested this extensively and I guess it will be dependent on how that app saves back the image (if they respect Apple Photos’ ‘non-destructive’ editing behaviour).
2. Affinity’s import image picker shows me the edited photo but loads the original. This feels a little disjointed.
3. Other 3rd party apps can import edited photos so I’m assuming this isn’t an OS restriction. I’ve just tested by making a number of ridiculous edits to an image and importing into Pixelmator and Hipstamatic. Both imported the edited image shown in their picker.
Sooo, if I’m considering point 3 above, is this behaviour a design decision on Affinity’s part or an oversight? If, it’s a conscious decision to only import the original, than point 2 seems an oversight.
Thanks again for your input. Would love your further take on this.
P.S. it’s worth my mentioning that this is far from an end-of-the-world scenario. It’s something that I do sometimes though, and this implementation seemed weird to me. Thanks.