ashf Posted June 12, 2019 Share Posted June 12, 2019 When I type arrow keys(i.e. down then left) while typing Japanese(refer p1), the same sentence I typed will be added next to the sentence I typed.(refer p2) on Japanese input, there are two steps to input text. First, type a sentence I want and this is input preview and the sentence will be highlighted.(means it's temporary and not regular text) Then when I type enter or return, it will be fixed as regular text and highlight on the text will be disappeared. Usually if I type down arrow while previewing, I can choose predicted sentence below input preview.(refer p3) But I can't choose predicted sentence on Affinity. While previewing input, commands to manipulate predicted sentence are assigned to arrow keys on Japanese input. So I'm supposed to be able to choose a predicted sentence with arrow keys. Kaki 1 Quote Link to comment Share on other sites More sharing options...
ashf Posted July 3, 2019 Author Share Posted July 3, 2019 Why the support is ignoring this topic and posting on another topic? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted July 3, 2019 Share Posted July 3, 2019 1 hour ago, ashf said: Why the support is ignoring this topic and posting on another topic? Perhaps because they process problem tickets in the order they were created, and that topic was created 2 days before your topic. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted July 3, 2019 Staff Share Posted July 3, 2019 Sorry we are so far behind since the 1.7 updates went live. Hopefully we can catch up with all threads soon, but frankly this doesn't seem to be working correctly yet so when it is addressed by QA staff it will probably just bump the report from the other thread as the cause and programatical solution are likely identical. Quote Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
ashf Posted July 3, 2019 Author Share Posted July 3, 2019 @Patrick Connor Please just check out another topic. You should realize that you are making serious mistake though you don't understand since you live in English environment. Quote Link to comment Share on other sites More sharing options...
Staff Sean P Posted July 4, 2019 Staff Share Posted July 4, 2019 Hi ashf, As I mentioned in the other thread I've now reproduced this issue and passed it on to development. Thank you for your help with this issue! 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.