musikinsnetz Posted December 14, 2022 Share Posted December 14, 2022 When typing a number into a size or position field (e.g. in Transform window or in Resize Document and Resize Canvas pop-ups), the first digit gets deleted in the instance I type the second. See my screenshots where I tried to type “800”. I’ve seen the “8” appear but vanish when I typed the first “0” This happens regularly but not everytime, and it happens in all three Affinity Suite v2 apps on macOS 12 Monterey on M1/M1 Pro MacBooks. Quote Link to comment Share on other sites More sharing options...
Staff Chris B Posted December 14, 2022 Staff Share Posted December 14, 2022 Hey musikinsnetz, I cannot reproduce that, nor have I seen it reported before. It sounds like it's being overtyped similar to how the Insert key works on a Windows machine. Do you use any applications for managing shortcuts/clipboard etc. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
TrevReav Posted December 14, 2022 Share Posted December 14, 2022 I also have this problem. Quote Link to comment Share on other sites More sharing options...
loukash Posted December 14, 2022 Share Posted December 14, 2022 22 minutes ago, Chris B said: nor have I seen it reported before It's been reported a few times. I vaguely remember that it may be related to non-English languages and corresponding decimal separators, etc. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Staff Chris B Posted December 14, 2022 Staff Share Posted December 14, 2022 I've had a scout but couldn't find anything to go on. The only bell that is ringing for me is some fields overtype but you can see a trace of the old text. I think this was Light UI specific. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
Milan M. Posted December 14, 2022 Share Posted December 14, 2022 In the macOS 12 Monterey system, you have to click 3 times and then it will write correctly. This problem does not exist in macOS 13 Ventura. Quote Link to comment Share on other sites More sharing options...
TomM1 Posted December 14, 2022 Share Posted December 14, 2022 Please enjoy this related thread. Quote website Mac mini (2018) 3.2 GHz Intel Core i7 64 GB • Radeon Pro 580 8 GB • macOS Monterey Link to comment Share on other sites More sharing options...
MikeTO Posted December 14, 2022 Share Posted December 14, 2022 5 hours ago, TomM1 said: Please enjoy this related thread. Oh, it's that bug, I didn't recognize it with a static screenshot. Thanks for catching this. 8 hours ago, Chris B said: I've had a scout but couldn't find anything to go on. The only bell that is ringing for me is some fields overtype but you can see a trace of the old text. I think this was Light UI specific. I think this one has been reported a few times. I think it might be an initialization issue where it can happen on first use. Quote Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF My system: Affinity 2.4.2 for macOS Sonoma 14.4.1, MacBook Pro 14" (M1 Pro) Link to comment Share on other sites More sharing options...
Staff Chris B Posted December 15, 2022 Staff Share Posted December 15, 2022 I've logged this as I've now found a few threads. Hopefully the developers can reproduce it. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
musikinsnetz Posted December 16, 2022 Author Share Posted December 16, 2022 Thank you all for your replies! I don’t know if it helps, but here’s some more information following up on some of the comments: no, I’m not using applications managing shortcuts or clipboards my macOS and with it the apps are set to (British) English, but I have customised it to use non-English decimal separators, like so: 4.321,5 instead of 4,321.5 my Affinity apps are always in dark mode, in contrast to the light mode I chose for macOS I have not found a way to securely reproduce the error. As I mentioned it doesn’t happen everytime and couldn’t figure out a trigger yet. Quote Link to comment Share on other sites More sharing options...
pjarnold Posted December 16, 2022 Share Posted December 16, 2022 The dropping of the first digit is happening in all three apps with macOS Monterey (not Ventura) and it only happens when I double click on a value to change it and start typing in the new value. If I use the tab key to navigate to the desired field and begin typing in the value, it doesn't happen. If I click before or after the value, which automatically selects the entire value including the measurement text, I can start typing in the new value and the first number is also not dropped. In the attached screen recording I am attempting to type in the value 456. On the first attempt, you will see the 4 is dropped as soon as the 5 is pressed. dropped-digit.mp4 Quote Link to comment Share on other sites More sharing options...
KipV Posted December 21, 2022 Share Posted December 21, 2022 I just discovered this problem in 2.0.3 so my guess is that the fix didn't make it into that release. I guess a lot of the bugs probably spilled over to the next update especially since 2.0 was so major. Quote New Internet Book Project | Another New Website Project Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted March 7, 2023 Staff Share Posted March 7, 2023 The issue "Typing in certain fields removes the initial character" (REF: AFP-5798) has been fixed by the developers in internal build "2.1.0.1720". 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. 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.