Hello,
In 7.9, when a field is selected and the onscreen keyboard comes up; the current text is highlighted and able to be cleared when the user begins to enter the new text.
It seems that in 8.1, any text in the field remains. This causes the user to either, press backspace repeatedly, or use the "clear text" button (that almost everyone mistakes for a button that closes the keyboard).
For reference, this is in Vision for both versions and specifically with the onscreen keyboard.
My question is if there is a way to either clear the text in the field once the keyboard is brought up, or have it selected so that new entries will clear it automatically and enter the new text?
Thank you for your collective knowledge and assistance!
You could write a script on the component so that when focus is gained, or when the user clicks on the component, it clears the text. For a text field, you will need to alter the behavior of the component, turn off 'Reject Updates During Edit', this prevents the text data from clearing properly.
1 Like
Thanks Tyler! While this would work for individual components, I am looking for a solution that focuses on having the keyboard behave how it did in 7.9. Rolling this out across a number of large installations would probably make these changes resource prohibitive.
The short answer is no.
I'm assuming you're on 8.1.28 or higher, with the new customizable touchscreen keyboard detailed here: New in 8.1.28: Custom Touchscreen Keyboard Support
Almost everyone?
For some technical context, the new keyboard is a total rewrite of the old one, but still subject to the same implementation limitations. What that basically means is there's no (practical) scripting "workarounds" for this, for instance - it's something we'd have to change first party. And you're the first person who's complained about it, to be honest, so we're not going to change it first party any time soon. Mild operator retraining is probably the easiest option.
If you want the old keyboard, exactly as it was, you can still invoke it manually via scripting, but there's no way to switch components to use it automatically across your project.
Hi,
You're correct, this applies to the new keyboard in 8.1.28+. This answers my question. I did experiment with the custom keyboard and, while those additions are exciting, the auto clearing or selection of the current text in the boxes is something I was asked to look into.
I didn't mean to come across as rude, but in the areas where we have upgraded to 8.1 and the new keyboard, the majority of the users I have observed see the "clear text" button and assume it closes the keyboard. This is probably just a function of them being used to most interfaces having an "X" in the upper right that closes a window.
Like you said, it seems the easiest option at the moment is to train them that they are able to clear the text with that button.
Thank you for your help!
1 Like