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
Related
I know there are similar questions on this topic. I have tried them all but nothing seems to work permanently. It seems it doesn't follow any pattern. sometimes for a long time it works just fine and sometimes out of a blue it just stuck and I couldn't make it work no matter what I try. It's really frustrating for me because I need my emulator to test different flavors simultaneously.
So please any one have any ideas?
If you are using windows and you have selected any RTL languages in the regional setting in windows setting, just change back to english (or any non-RTL language) as you open android studio (or while compiling gradle if you are not using offline mode). It is a weird bug that I thing have something to do with parsing.
I am using Qt Widget QCompleter in combination with QComboBox and the completion mode is set to QCompleter::PopupCompletion. It works fine on Windows, but app crashes while typing text in the QComboBox on Android platform. If I change the completion mode to QCompleter::InlineCompletion, then it works fine on both Windows and Android platforms.
Has anyone experienced this issue and found some solution. Please guide or suggest some other alternative. I want to run the app on Android with Popup Completion mode as it runs on windows.
I have built hybrid app with Sencha touch 2.3 and till recent it was working fine but i recently updated the Android System Webview via Play Store (i have moto g running android 5.0.1) and now i am encountering various bugs in UI as follows :
The selectfield picker does not work correctly now. It behaves randomly. The store bound to it has data but no items are displayed in the picker when it opens. At times items do get displayed but you cannot select the items at bottom because picker always resets the selection to the item at top.
Few screens show up blank initially when rendered for the first time. As soon as user touches the screen and moves a little bit the whole screen/view becomes visible.
Also there might be other things that might have broken after updating the webview which i might not have discovered but this a big issue as far as developing for android is concerned with sencha touch. The webview updates are now pushed Over the Air and hence many things may break in future.
I also confirmed the above bugs in older versions of android wherein the webview has not been updated and the above bugs do not show up in.
I am thinking of using crosswalk as the solution to the issues with the webview. Anyone with the same issues or any tips regarding a fix ?
I ran into a similar issue with my Sencha Touch app (almost nothing rendered). Here is the workaround I used which seems to work great:
http://trevorbrindle.com/chrome-43-broke-sencha/
Thanks #Ian. The link was tremendously helpful and it solved the issue for now. Sencha has not officially released a build with these fixes so the overrides are the only solution right now.
For anyone facing same issues here is one more link from the Sencha Forums where all the issues sencha frameworks are facing with Chrome 43 are stated and solved.
https://www.sencha.com/forum/announcement.php?f=92&a=58
I am also stuck with same issue and i found solution we should not update the chrome. Better download 42.0.2311.152_chrome64_installer which is offline exe for chrome.
I have made HTML5 application which is using vmoss platform, similar to phonegap. The application was running smoothly on samsung galaxy 10.1 tab with android version 4.0.4. After the client updated the device to android 4.1.2 now he is complaining of following issues.
Calendar control not working in new version
Text box controls having focus issues
Application GUI Issues because response is very slow
The page where issue of slowness comes is the page where child pages are loaded inside one of its div.
Can someone tell me, is it android os update issue or what?
i think it's because of the platform not updated to work/cope well with version 4.1.2
this one is vmoss platform issue.
Better try to run simple Html page with all these control without using the VMOSS at backend and see if there will be any issue.
Some time the version of Jquery doesn't fully support by the browser.
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.