Minor bug in Designer 2 for iPad- text effects dialogue

[PJ design]

When using the text effects dialogue in affinity designer 2 for iPad, there are right arrows to go to a sub-dialogue. When returning to the main dialogue, it sometimes comes up blank. When this happens the dialogue is unusable. A workaround is to close the file and reopen it, which resets the dialogue.

[Paul Mudditt]

On 11/15/2022 at 2:06 PM, PJ design said:

When using the text effects dialogue in affinity designer 2 for iPad, there are right arrows to go to a sub-dialogue. When returning to the main dialogue, it sometimes comes up blank. When this happens the dialogue is unusable. A workaround is to close the file and reopen it, which resets the dialogue.

Sorry for the long delay in replying to this request but the Serif team and the secondary support team of simply users like myself have been answering as many as possible as quickly as possible.

I think this problem may have been fixed in the last update, can you do a screen recording if it still occurs and post it here?

Apologies again for late response.

[Dan C]

Hi @PJ design,

Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here.

I can confirm I recently discovered this issue and it is logged with our developers, it seems to occur when quickly returning through at least 2 'sub levels' of the Text Studio, as shown here - 

 

Hopefully this should be fixed in an upcoming update

[PJ design]

Thanks for looking into it, hopefully an easy fix.

[Affinity Info Bot]

The issue "[iPad] Quickly returning through multiple studio menus leaves studio blank until re-entering document" (REF: AFD-6341) has been fixed by the developers in internal build "2.1.0.1781".
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.