Various Bugs found

[safoster71]

Greetings Affinity!  

Good job so far!  Don't let the whiners get you down!  Just a few things i've found in my playing with designer on ipad (ipadpro 12.9 3rd gen - ios 16)

>When you swipe three fingers and get the new contextual menu (LOVE this idea) when you hold a finger down, and get the additional list - any click on that additional list leads to a app crash.

>After adding all my fonts to v2 (thanks alot apple). i found a it strange, that when i select said added font, the "name" in the text menu on the side and at the top is incomprehensible - looks like Chinese writing.  (used ios to try to translate - it came up with ??????)

and now for the "gee, let me see how far i can go to break things" category

> step 1, place/embed (on an ipad!  wow!) a older affinity file of a vector pumpkin i drew for a project last year.

>step 2, place a filled box underneath.

>step 3 - decide to try a mesh distort on said embedded afdesign file.

>>result - see attached 🙂

 

All in all great effort here guys!  Just a few loose ends to tidy up and we are gold!

Thanks all!

Scott

 

[liumingming]

same

[Sean P]

Hi safoster71,

Thanks for letting us know, 

We do have the first two issues logged with development. Regarding the Mesh Warp - unfortunately as it stands it is not intended to work on placed/embedded files, and can only be used with actual vector objects in a shape.

[_Th]

On 11/22/2022 at 9:42 AM, Sean P said:

Regarding the Mesh Warp - unfortunately as it stands it is not intended to work on placed/embedded files

Hoping that this might be reconsidered as this would be a huge help. Thanks.

[Affinity Info Bot]

The issue "[iPad] Fonts installed from creative cloud show on context toolbar with name in Chinese " (REF: AFD-6170) has been improved by the developers in internal build "2.1.0.1736".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.