Hello,
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 ("."), does not work in phone. Works fine in tablet. I tried removing all key validations for the amount field but still the same. Anyone have experienced this one on real device?
By the way, I added the mobileSetKeyboardType "decimal" on preopencard
Also I tried using mobileSetKeyboardType "numeric" but no luck.
EDIT: This is working on my phone having android version 4.0.4. It is not working on my other phone having android version 4.1.2
Thanks,
-jun-
mobileSetKeyboardType "decimal"
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: mobileSetKeyboardType "decimal"
Hi Jun,
Not quite sure what your question is. I always use
in the script of a field to open up the numeric keypad for entry into a text field. On all of the devices I've tested, this command has worked as expected.
I've also never seen the issue of a period "." not working. I wonder if that problem is specific to the device on which you're testing your app.
Tell me if I misunderstood your question.
Hope that helps,
Jacob
Not quite sure what your question is. I always use
Code: Select all
on openField
mobileSetKeyboardType "numeric"
end openField
I've also never seen the issue of a period "." not working. I wonder if that problem is specific to the device on which you're testing your app.
Tell me if I misunderstood your question.
Hope that helps,
Jacob
Re: mobileSetKeyboardType "decimal"
Hi Jacob,
I've emailed this problem to runrev support. They said "this is a specific bug with LiveCode 5.5.5 and Android 4.1.2". I got an email/reply below from their support.
"I can confirm that I am able to replicate the issue from this stack. After further
investigation this seems to be a specific bug with LiveCode 5.5.5 and Android 4.1.2.
This bug seems to be resolved in the 6.0 release of LiveCode. You will be able to
test this by downloading the community version of LiveCode from your store account
(currently version 6.1.0)"
Thanks,
-jun-
I've emailed this problem to runrev support. They said "this is a specific bug with LiveCode 5.5.5 and Android 4.1.2". I got an email/reply below from their support.
"I can confirm that I am able to replicate the issue from this stack. After further
investigation this seems to be a specific bug with LiveCode 5.5.5 and Android 4.1.2.
This bug seems to be resolved in the 6.0 release of LiveCode. You will be able to
test this by downloading the community version of LiveCode from your store account
(currently version 6.1.0)"
Thanks,
-jun-