Imagine a normal keyboard in android (like English). When pressing and holding A for a while, a new menu with á, ä and other buttons popups up. And while still holding the first finger down on screen, you slide it on top of another of those buttons. As you slide it over a button, it gets into highlighted mode , and when you slide out the highlighting is turned off. If you release the finger, the popup buttons disappear. If you held the finger over one of the buttons, that button's character is being typed into the text field
How can i achieve this functionality on andriod. Any help will be deeply apreciated.
Related
In my activity, I have a multiline EditText that takes a big space on the screen. When I click on it, I enter the edit mode and the soft keyboard shows up. So far so good
Now I want to select the text. So I long press on it, and the selection handles appear. The problem is that when I select multiple lines, the whole layout of the activity will be pushed up to be able to see the selection above the keyboard. But it also pushes up the selection menu that allows to interact with the selection (like Copy, Search, etc.), so the selection is useless!
So best solution would be to make sure the menu stays visible, alternative solution would be to hide the keyboard when selection happens so that nothing is being pushed up.!
As you can see on the screenshot, the menu is almost gone because the selection is right on top of the keyboard, but without the keyboard it should appear just fine
Most of the time (but not always), when I finish typing in a or and the soft keyboard hides, the view area is left raised with a black space on the bottom. Clicking, tilting or otherwise engaging the phone corrects the screen. However, user's first motion is usually pressing , but if you click submit it jumps down and you actually just click on the text area again. How do you stop this and get the screen to reset after the keyboard closes.
Take a look at you AndroidManifest.xml
http://developer.android.com/guide/topics/manifest/activity-element.html
I think you need to change android:configChanges.
I have the exact same problem what i did was handle hidekeyboard even in javascript and do something like window.scrollTo(0,0) or $("input[type=text],textarea").blur();
This will cause the the screen to get back to normal position
But there is just one problem when click from input field of type = text to a input field password it internally hide the keyboard which causes the hidekeyboard event to fire and scrolls the screen to top. This is the only side effect of this
Let me know if you find the solution for this
I'm using the v16 API and having problems with where the popup is being placed when the onscreen keyboard is displayed.
The first problem is that if the EditText is at the bottom of the screen, when I touch the field to open it for editing the popup is displayed below the control and the immediately covered as the keyboard appears. It doesn't reposition itself above the EditText until a keypress triggers my validation code to fire again on the new value.
The second problem is that when I close the keyboard and the ScrollView containing the text scrolls back down from where it positioned itself to show the EditText above the keyboard the popup remains placed on the upper half of the screen instead of where the EditText is until I touch something else on the screen (triggering the ScrollView to do a redraw???).
Unfortunately that popup has various problems like this :(
Perhaps a simple solution in your case is to forcibly invalidate the UI when the keyboard has displayed and dismissed? Can't recall if the Popup will reposition if the EditText is invalidated, but worth trying as the alternative may be to re-implement.
Checkout my android-formidable-validation lib on github, it re-implements...though has its own problems - if you go down that path, why not give me a hand with some contributions ;)
I am trying to create a menu that will behave much like the on-screen keypad of Android, wherein when press-holding a key with accented characters like "i", a popup menu for the accented characters is displayed. Then sliding the finger into the button of any accented character within the popup menu highlights/selects the button, and finally releasing the finger, inputs the accented character into the target textbox. I have seen this behavior in Android v2.3, but not on the older versions. Not sure if this is a new feature?
I would like to know how to handle the touch gesture such that main button (e.g. "i") will react to press and hold touch events, and then after the popup appears, the button for "ï" will react to the point and release touch events? The user will not need to release the finger, thus the motion will be a press-hold-slide-release between 2 buttons.
I have tried to find the code used in the Android keypad but was not successful as I only got directed to CharacterPickerDialog which does not show the press-hold-slide-release between 2 buttons, since it requires the user to release the finger before selecting a button in the popup menu.
Hope anyone can provide some info and insights on this. Thanks in advance!
I am using AutoCompleteTextView (ACTV) in my app.
The ACTV is vertically positioned around 100px from the top.
When user clicks on it, software keyboard opens and the suggestions dropdown appears below the ACTV.
Now I am getting to the bug - when user taps on some suggestion from the dropdown, the dropdown jumps above the ACTV!
So if I want to select a suggestion, I have to tap on the screen twice - firstly when the dropdown is below and then after it jumps to the top (by "jumps" I mean it immediately disappears under my finger and opens above).
Any idea how to circumvent this bug?