Brian_J Posted May 27 Share Posted May 27 I’m not sure if the OP and comments are all related to use of an external keyboard. Moving the cursor with the iPad keyboard is also broken. Long-pressing the Spacebar places the cursor at the top-left of the text frame and the cursor can’t be moved by dragging. Quote Windows 10 22H2, 32GB RAM | Affinity Designer/Photo/Publisher 2 (MSI/EXE) Link to comment Share on other sites More sharing options...
BAIYANGDN Posted May 27 Share Posted May 27 Yes, all keyboards can't move the cursor left and right. Brian_J 1 Quote Link to comment Share on other sites More sharing options...
Brian_J Posted June 4 Author Share Posted June 4 @Affinity Info Bot The issue is still occurring in V2.5.2 when using the iPad keyboard — the cursor cannot be moved by long-pressing the Spacebar. BAIYANGDN 1 Quote Windows 10 22H2, 32GB RAM | Affinity Designer/Photo/Publisher 2 (MSI/EXE) Link to comment Share on other sites More sharing options...
BAIYANGDN Posted June 4 Share Posted June 4 我测试也存在同样的问题，系统自带的键盘无法空格键移动光标。@Affinity 信息机器人 Quote Link to comment Share on other sites More sharing options...
Staff EmT Posted June 11 Staff Share Posted June 11 Hi @Brian_J and @BAIYANGDN I've moved your comments from here into a new post as this is a different issue. I have been able to reproduce this and will get it logged up. Brian_J 1 Quote How to format a bug report | List of V2 FAQ's | Affinity Photo (V2) Tutorials | Affinity Designer (V2) Tutorials | Affinity Publisher (V2) Tutorials Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted July 5 Staff Share Posted July 5 The issue "[iOS] iPad: Long-pressing spacebar puts caret at start of text frame and cannot be moved by dragging" (REF: AF-3440) has been fixed by the developers in internal build "2.5.5.2589". 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 @Affinity Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.