Touches on screen to select drop down menus/ or move the screen/ are interpreted as writing and show in text entry fields. Send some apps, including Samsung Contacts, for example, have trouble with writing text in a field.
Troubles moving the cursor/instruction point or selecting and manipulating other
On screen elements that are interpreted as text entry and any combination of periods or other characters pop up in the text field be the expected action.
This is seemingly very unfinished in it's operation.
Even something as simple as, in Samsung Contacts, entering a contacts relationships. Attempting to select the selecting the drop down menu to select whether the relationship is a Mother, Father, Sibling, etc is often non-functional.
The work around is having to switch between reserving the stylus for only text entry, and using a finger to point and select.
EDIT: JUST HAPPENED AGAIN:
Reddit: Finished entering text. Went to hit the "post" button with the stylus.
GOT A PERIOD in the text field. Doesn't seem like even basic screen elements are understood or respected..
This happens on other apps too haven't had ONE UI 7 too long (Galaxy S21 Ultra) but patience waiting for fixes is getting thin.
I'm committed to the stylus. Use it Miss Everytime I interact with the phone. In any app.
While I love the integration of text recognition, it is a huge step back for a stylus user to alternate between the two modes when stylus is in hand.
Actions like using the slider bar on the side of the screen can also be misinterpreted as attempts to enter text characters.
While I used Samsung Contacts. as an example, this behavior is pervasive.
Often, I use the Swype with my stylus on a keyboard. Then, when I'm forced to touch the screen with a finger to manipulate other elements the keyboard disappears.
Maddening to chase these elements.
It is in the verge of greatness... But these seemingly small things make things tedious.
Please know that the example voted is only one of many aid that exhibit issues. Another easy to demonstrate area would be to try and read comments under a Facebook post. And to possibly respond. The cursor is already flashing in the comments field, so attempting to manipulate the screen to read through comments invariably creates nonsense string of characters instead of moving the view.
Which may illuminate that action by app developers is necessary to not pre-ppsition a cursor in a text entry field? This may be likely separate, but related?
One UI 6 used to require selecting field for text entry first with quick touch, them entry with on-screen text entry with keyboard, it writing in text capture part of Gboard. With introduction of writing in fields this has become an issue.
