Hello.
Is any update in recent corona versions that overpass the expression: numericField.inputType = “number” ??
It only shows me complete keyboard. Tested in 2 devices, and other options like “phone” also don´t . It usually works…before.
Thanks.
Make a sample project that demos this issue and share it here as a zip file containing the source.
What version of Corona are you using specifically. Give the version number. Ex: Latest daily build as I type this is 2018.3228
Also, what specific devices, os, and os versions are you seeing the issue on? This is the kind of detail you should always share when you say something doesn’t work. Also, you’ll need to specify it anyways if you end up filing above.
That said, I think if you share your demo project with us, we’ll be able to help you.
I got tired of waiting, so I tested this on my Galaxy Tab 4 (SM-T230NU) running Android 4.4.2
I wrote a sample and built it with 2018.3228. I installed and test it without issue.
This is the pertinent code:
local defaultField = native.newTextField( 150, 150, 180, 30 ) defaultField.inputType = "number"
This is the sample:
https://github.com/roaminggamer/RG_FreeStuff/raw/master/AskEd/2018/02/numericKeyboard.zip
Here is an Android APK:
https://github.com/roaminggamer/RG_FreeStuff/raw/master/AskEd/2018/02/numericKeyboard_apk.zip
In the future, please supply us with the details about your build and test devices, as well as one of the following:
- Micro sample project (like the one I provided) - OR -
- At least a short and clear snippet of code (like shown above; including formatting) so we can see what you are doing.
Sorry.
It was a big mistake from my code.
I was thinking tha put the “number” in the addeventlistener was the trigger to said to corona that i want a numeric input.
[lua]
f1 = native.newTextField( 400, 210, 200, 50 )
f1.text = “1000”
f1:addEventListener( “number”, textListener )
[/lua]
Make a sample project that demos this issue and share it here as a zip file containing the source.
What version of Corona are you using specifically. Give the version number. Ex: Latest daily build as I type this is 2018.3228
Also, what specific devices, os, and os versions are you seeing the issue on? This is the kind of detail you should always share when you say something doesn’t work. Also, you’ll need to specify it anyways if you end up filing above.
That said, I think if you share your demo project with us, we’ll be able to help you.
I got tired of waiting, so I tested this on my Galaxy Tab 4 (SM-T230NU) running Android 4.4.2
I wrote a sample and built it with 2018.3228. I installed and test it without issue.
This is the pertinent code:
local defaultField = native.newTextField( 150, 150, 180, 30 ) defaultField.inputType = "number"
This is the sample:
https://github.com/roaminggamer/RG_FreeStuff/raw/master/AskEd/2018/02/numericKeyboard.zip
Here is an Android APK:
https://github.com/roaminggamer/RG_FreeStuff/raw/master/AskEd/2018/02/numericKeyboard_apk.zip
In the future, please supply us with the details about your build and test devices, as well as one of the following:
- Micro sample project (like the one I provided) - OR -
- At least a short and clear snippet of code (like shown above; including formatting) so we can see what you are doing.
Sorry.
It was a big mistake from my code.
I was thinking tha put the “number” in the addeventlistener was the trigger to said to corona that i want a numeric input.
[lua]
f1 = native.newTextField( 400, 210, 200, 50 )
f1.text = “1000”
f1:addEventListener( “number”, textListener )
[/lua]