I thought this was an issue at first, but all of the reported problems are coming from users with the US English locale with a period as the monetary separator unit.
On Jan 13, 11:24 am, niko20 <[email protected]> wrote: > Hi, > > This sounds like a language input problem. Some languages use the > comma for numeric values instead of the period. On those languages a > period will result in a comma being input. I ran into this same issue > in my app a long long time ago. Just parse the data they entered and > replace any commas with periods (if you are expecting a number value > that is). > > -niko > > On Jan 13, 8:16 am, Chris McCurdy <[email protected]> > wrote: > > > I've had a few users report issues on the Motorola CLIQ and Samsung > > Moment of when they press the period key on their hardware keyboard, > > nothing happens on screen. This is somewhat expected, since I'm > > restricting the input into the field to be a valid currency value. But > > for some reason, their phones are sending a comma (,) when they press > > the period (.) key. I've never seen this issue on my G1, and it seems > > to work fine on all software keyboards. Here is my class I use to > > restrict the input:http://pastebin.org/75509 > > > I was wondering if anybody had heard of any problems like this, and if > > so, what was the solution? I suppose I could remove the class to > > restrict input, but it seems like it would still send a comma and > > create an invalid number.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
