I am facing same issue as this post on Android: QML TextField text erroneously capitalized on device ... All letters are capitalized for TextField control. I have mixed TextField elements where for example when I set echoNode to password, the letters are not capitalized (no issue), while fields with normal echoMode get the issue, which makes me confident its under control of either Android or Qt code.
I switched to investigate from Android side and found this post My Phone Is Capitalizing Every Word which suggests that this problem occurs only when auto-capitalization is enabled on device... I tested it, turned off auto-capitalization on device and the issue disappeared ...
After some investigation I found that most Android apps are build with auto-capitalization aware code, for example this post Why is my Button text forced to ALL CAPS on Lollipop? show solutions with Android Java code .. I wonder if this is a Qt bug or there is something to control it, for example, with QtAndroidExtras classes? while trying to avoid the use of Qt keyboard, I believe/hope there could be a solution from Qt side.
Related
We are using a teensy 2.0 on an Android 4.4 or Android 5.x device. We want the teensy to emulate a keyboard.
When a push-button is pressed a small letter should be send. After releasing a button, a capital letter should be send.
We have used teensyduino to write the necessary code. It's super simple to do like:
Keyboard.print(char('A'));
....
Keyboard.print(char('a'));
....
Somehow on windows machines it works fine, on Android, we see that the "keys" got jammed and a letter is send multiple times or it's even stuck in a loop.
When using the C code example (like shown here https://www.pjrc.com/teensy/usb_keyboard.html) it works on Android.
Any ideas what could cause this problem? Seems like the USB library when using teensyduino is different.
Any guidance is appreciated.
So I have an issue with the fairly new Unity 4.6 UI system.
I have a multiplattform project and everything works fine (pc/ ios) but my input fields for the user to log in sometimes don't open the Touchkeyboard, or it is not possible to focus them.
I guess I have to open the keyboard manually, focus the inputfield and do the navigation myself, but there is not a lot of documentation about it...
so my questions:
How do I hide the mobile input field (the one above the keyboard) via Script on run time?
How can I keep the keyboard always open, but still use the submit-event of the keyboard?
Any other cool ideas which could fix my issue?
I am running on my test device android 4.1.2, 4.2.2 and 4.4.2 and I can recreate that problem on all of those, even though 4.4.2 seems to be the worse.
Thank you very much my brave Unity UI warriors!
Make sure you are using latest unity version, they had a few bugs related to InputField in 4.6. If that doesn't help, you should try patch releases.
How to hide InputField additional input box in unity3d
In farsi letters are attach together to form writing scripts. However when I save HTML pages using "UTF-8" or "Windows-1256" encdoings, and try to display them using webview in android, letters are diplayed seperately and in left-to-right direction (instead of RTL).
I should notice that this case is not happening in phones supporting farsi.
Correct form should be like this (snapshot from phone supporting farsi):
Bad-formed text happens in phones not supporing farsi (Persian):
It should be noticed i've used persian font in both cases.
I also see some solutions for normal Strings in java which changes character on by one in this
question
My question: Can i fix this cases (or it should be fix by phone vendors)? if possible what is solution?
I hit this bug a lot when I was doing keyboards. The problem is that the build in canvas.drawText function in Android didn't support RTL languages. There was a patch for it, but it wasn't part of the default build of Android. So only models going out to those parts of the world that used it tended to have it. Unfortunately I know of no way to test whether it has the patch. And if it doesn't, there's no way to fix it. You could try reversing the text, but then you'd break devices which did have the patch.
Long story short- there is no way to fix it. However, I'd be shocked if Google hasn't picked up the patch in mainline by now (it existed back in the 2.2 days), so its a shrinking number of phones effected.
You can try making html with reverse font sequence! just write a windows app to get font and deliver reverse one, and use it in your android device
I am experiencing a strange bug only on Samsung mobile phones that are running Androi 4+.
With Adobe AIR, every textInput is not suitable for use. The beginning of the entered word is repeated on every char input.
Here is the behaviour:
When I enter "ABC"
The input text is "AABAABAABAABAABAABC" (or sometimes known words from the dictionary)
It seems to add the whole content of the text input on each key press. Making the words repeated several times.
It also seems to be an autosuggestion (from the phone's dictionary) related bug.
The textInput is declared this way:
<s:TextInput id="tin" autoCapitalize="all" autoCorrect="false"
maxChars="19" restrict="0-9A-Za-z_\-" width="100%"
itemCreationPolicy="immediate"/>
Others devices are just running fine, even on HTC running Android 4.1, older versions or others manufacturers.
This bug has also been seen on Swype keyboards (third-party system keyboards).
Do you have a workaround to make it work?
Thanks
EDIT: The worst behaviours are caused by the restrict property. Without that, the text input is still bugged, but less. I filed those bugs at bugbase.adobe.com, please vote for it:
TextInput's restrict attribute makes user interaction totally unusable
TextInput's autoCorrect attribute has no effect
TextInput component ignores autoCapitalize, autoCorrect, and softKeyboardType properties when setting a custom skin
Regarding the mobile textInput, Adobe has really screwed us with Flex 4.6.
Set the skin class to spark.skins.mobile.TextInputSkin and you should be good to go.
In a web page running on an Android browser (on a Galaxy Nexus), is it possible to disable the feature that suggests words (in a box above the keyboard) and underlines them as you type?
I tried autocomplete="off" autocorrect="off", but it had no effect.
In experiencing the same issue I did some digging and discovered it is a bug in Chrome for Android. Those HTML 5 attributes are intended to do what you are looking for but are not properly supported in Chrome for Android(they do work for iOS). It appears to just recently have been fixed and hopefully should be released in an update soon.
https://code.google.com/p/chromium/issues/detail?id=303883&q=autocorrect&colspec=ID%20Pri%20M%20Iteration%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified
Also feel free to Star the issue to help boost the ranking...
In a web page running on an Android browser (on a Galaxy Nexus), is it
possible to disable the feature that suggests words (in a box above
the keyboard)
No
and underlines them as you type?
No
Those are user preferences and moreover if the user bought a keyboard app, it can have its own setting to auto-complete.