on this possibility I have already thought, but it is not a "clean" solution.
I find it better, if the keyboard is set to upper-case letters by the Code.
unfortunately I do not understand what he did exactly.
I Initialize the EditText (only once) in which I load it because it was created with the designer.
I can not make any adjustments to this before.
I the EditText was added through a Designer Layout you SHOULD NOT initialize it!!
You just need to have it dimed in the appGlobals sub, and for that, you use the "generate members" in the designer's tools
I the EditText was added through a Designer Layout you SHOULD NOT initialize it!!
You just need to have it dimed in the appGlobals sub, and for that, you use the "generate members" in the designer's tools
that's what I'm exactly doing!
I load it whith the complete Layout.
If I initialize it and set it before (which is not correct!), it would be reset by loading the layout again
so I do not understand what Smee does. Do he creates it in the code or was the error at other place
here a small test project. I hope it helps.
In the field Call (dim as lbl_Call), the keyboard is only to enter uppercase letters.
(CapsLock should be activated)
CapsLock is activated. I'm using B4A 7.3, my target was API Level 24, Intel Atom (x86) CPU/ABI. The only way I could circumvent the capitalization was by picking a auto-corrected/suggested word that includes lower case characters.
i Test with Motorola/Android 6.x and Samsung/Android 5.x Device, not in Emulator.
Is there a difference (o.k., other API Level, but it was add in API Level 3)??
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.