This is a question re the android SIP (that's what we call it on WP7). Please see the clip at https://dl.dropbox.com/u/39662979/AndroidEmulator.png.
This is a demo app in the commonsware book on android development. It displays textboxes for longitude and latitude and shows a keyboard allowing the digits 0 - 9. * and # to be entered. Of course longitude often requires a negative number but how does one type the minus sign?? I've tried all of the other keys - I'm able to bring up other character sets but no minus sign.
The book shows a minus sign being entered but eluding me.
thanks,
Dean
Had a similar issue on my Galaxy S3:
The numeric keypad of the stock Samsung keyboard shows the digits 0 thru 9 plus one more key with a period and a minus sign combined: .-
Took me quite a while to find that the minus sign requires a double tap, not a long press.
It may be that your keyboard doesn't have the "-" due to your language setting. I'd recommend adding another keyboard (probably the US keyboard) via device Settings and switching to the US keyboard while you're testing.
That means the program is not working correctly
If you run the application on a device or emulator that is configured for English, there is a key, marked with what in English is referred to as a "minus sign" (upper-right button on keypad), that can negate the number typed into the EditText:
You will notice that, in your screenshot, the keyboard is different:
In part, this is because your emulator is not configured for English. It is configured for some other language. You can tell this because some of the keys have Chinese, Japanese, or some similar character set on them.
I do not know precisely what language your device or emulator is configured for. I do not know if one of those keys either is a negation, or leads to a secondary keyboard that offers negation. My guess is that the key in the lower left corner would switch to alternate keysets, but that is just a guess.
My recommendation would be for you to configure your emulator to be for a language that you speak. Then, perhaps the keyboard will be more intelligible to you.
Related
If I try to use altgr+v (#) in an android emulator's editText, I cannot write the "#" sign.
The altgr is the 2 finger gesture (zoom) by default.
Any other shortcuts or some solution for this?
As it can be seen and pointed out in below screen
Take your mouse and click at the pointed area you will find new keyboard option and done
You can use your hardware keyboard that is attached with your computer or laptop. To use your hardware keyboard follow below steps
Open AVD manager
Go to edit option of your desire virtual device
Select Show Advance setting button
At the bottom you will find enable keyboard option mark that option check
It's still open bug in Google issue tracker from 2017 🤷♂️ https://issuetracker.google.com/issues/37142228
This is an old question but still a valid one, since i suffered from that too recently.
Is not possible to type "#" using a keyboard with a language that requires to use Option+Q or Option+2 in Mac, or AltGr+Q in windows, the emulator does not accept the use of Option nor AltGr keys
the solution is to change the language of keyboard to english ABC so the # is accesible with Shift+2, in other languages, the number 2 has (") but in english ABC the number 2 has the (#) when you use shift.
Go to settings and change the configuration of your keyboard, in Mac you can just click in the keyboard icon showed in the top bar
I have a problem on my app in android. I added a code mobileSetKeyboardType "decimal" to show the decimal keyboard to input an amount. But it seems the Dot (".") button, does not work in phone. Works fine in tablet. I tried removing all pKey validations for the amount field but still the same. Anyone have experienced this one on real device? And how did you solve it?
By the way, I added the mobileSetKeyboardType "decimal" on preopencard
Note: I am using Livecode.
I'm posting this as an answer because that allows me to include a formatted script.
What happens if you put the following handler into the field script:
on rawKeyDown theKey
set the text of me to theKey
end rawKeyDown
Don't put this script anywhere else. It might make your stack unresponsive.
What language is your device using? If it is English US, what happens if you change it to English UK (or the reverse, or just change it to either option if you're using a different language)?
The real device keyboard can be a modified version of standard Android keyboard, so its behaviour may vary from device to device.
I have a login screen on my app which accepts a CPF as login (CPF is an unique number identification that every Brazilian citizen have, e.g: 10546819546), but it can also accept passport numbers as the login, and these may have letters on it.
My problem is that I want the keyboard, when it pops up, to show to number/symbols "view" before the default alphabet one. Changing the inputMethod to phone or number does not solve my problem, because as I said, the login may contain letters.
I've seen some explanations to questions somewhat similar to mine but all of them either didn't solve my problem or it was too overcomplicated.
This is merely a small adjust to slightly improve user experience and entertain me developing the app, so if the solution is something like "override the default keyboard, make a custom component" etc, I'll just leave it alone.
TL;DR: I want to show the number/symbol soft keyboard before the letters one.
Unfortunately when it comes to the soft keyboard you are somewhat at the mercy of whoever made the one the user has their device set to. Lots of devices come pre-loaded and defaulted to the swype keyboard. But many others have soft keyboards that were made by the manufacturer of that device. It it up to whoever created it to decide how the keyboard reacts to the android:inputType that you pass to it. It is possible that some of the ones out there right now actual have the behavior you are looking for when you set them to number or phone. I just checked it out on my sidekick and found that it was the same as yours both number and phone provided no way to input letters.
I'm adding some mobile usability optimisations to our site. As part of this I am tweaking the type attribute of textfields, to give the user the best input tools for the expected data type.
One issue I have come up against in touchscreen mobile devices is that browsers on different OSes, and even different browsers on the same OS, show different onscreen keyboards when input type="number" is used.
Safari on iOS 4.3.3 (iPhone 4) and Chrome on Android 2.3.4 include a decimal point, but Firefox on Android 2.3.4 does not.
I have tried adding the step attribute (step="0.1") with no improvement in Firefox.
If I cannot show the decimal point I will need to show Firefox the full QWERTY keyboard, which is obviously not going to make for the best user experience. It also raises the issue of browser/device sniffing. Either I'll need to make QWERTY the default, and show the numberpad to the handful of devices I can actually test on, or make numberpad the default, and switch back to QWERTY on devices which I know this will break on, the latter option being far less robust as I cannot test on every device ever made.
Testing for support for input type="number" is not a fix, as obviously the browser does support the element, it just doesn't offer enough keyboard options to enter all number types.
So.. I was wondering if anyone knew of a way to test for the presence of a certain key (such as the decimal point) in the keyboard the browser/OS assigns to the input type, and/or if anyone else has some better suggestions, as I'm quite new to mobile devices.
I should also mention that I am using JavaScript here, as this is a website, not a native App.
Thanks :)
Unfortunately, firefox does not support numeric input type. However, you can still try using these additional HTML attributes for making an input field prompt the user for numeric input
inputmode='numeric'
pattern='[0-9]*' //this makes it show only the numbers 0-9 without all the slashes and dashes and everything. Ignore this if that's not what you want
When I run a program on my android emulator most of the keys are in English. However, on both lower corners there are buttons that look like they are from an Asian language. Also, I am using textAutoCorect, but only Asian characters pop up instead of English words. I know it is not my code, so how would I go about fixing this?
Is this happening when you type into a textedit or something? if so then you want to long click onto the textedit and then select input method and then android keyboard.