inputType for texField Decimal

Getting Started Newbie Questions
#1

So according to here: http://docs.coronalabs.com/api/type/TextField/inputType.html

I should be able to choose “decimal” as input type. However I just tested this with a debug build on my Galaxy Nexus and the native keyboard that popped up was the regular one, allowing me to enter anything.

I need to only allow numbers, the “-” for negative numbers, and decimals.

I guess I could make some kind of checker when the box loses focus yelling at the user to only enter valid things, but that’s really silly seeing as the native keyboards for IOS and Android have specific keyboards for numbers.

#2

Corona currently does not support the “decimal” keyboard on Android yet.

Believe it or not, getting a decimal keyboard type to work consistently between Android devices has proven more difficult than expected.  Some devices’ virtual keyboards simply ignore the setting.  We think we’ve found a solution to this, but it involves rewriting our text field code on Android, which we’re not prepared to do yet.  Even then, in my experience with Android, you have to treat Android keyboards like PC keyboards… meaning that there is nothing to stop the end-user from typing in whatever key they want on the keyboard.  Especially if it comes from a physical keyboard like what comes on a Droid or a Bluetooth keyboard.  Ultimately, this means that you should always validate the received text input.  We’ll still look into adding “decimal” keyboard in the future, but heed my warning, some virtual keyboards may simply ignore it.  Especially 3rd party keyboards that the end-user can download and install on the device.

#3

That’s good advice. Thank you.

#4

Corona currently does not support the “decimal” keyboard on Android yet.

Believe it or not, getting a decimal keyboard type to work consistently between Android devices has proven more difficult than expected.  Some devices’ virtual keyboards simply ignore the setting.  We think we’ve found a solution to this, but it involves rewriting our text field code on Android, which we’re not prepared to do yet.  Even then, in my experience with Android, you have to treat Android keyboards like PC keyboards… meaning that there is nothing to stop the end-user from typing in whatever key they want on the keyboard.  Especially if it comes from a physical keyboard like what comes on a Droid or a Bluetooth keyboard.  Ultimately, this means that you should always validate the received text input.  We’ll still look into adding “decimal” keyboard in the future, but heed my warning, some virtual keyboards may simply ignore it.  Especially 3rd party keyboards that the end-user can download and install on the device.

#5

That’s good advice. Thank you.