Number format with spaces cause troubles at parsing time
Reported by Virgil Dupras | March 21st, 2012 @ 03:57 PM
My number format contains spaces, so when I modify a number in moneyGuru I have to delete the space first, otherwise the old number comes back after hiting Enter. That would be great to take spaces into account during entry validation.
Comments and changes to this ticket
-
Virgil Dupras April 6th, 2012 @ 05:59 PM
- State changed from “new” to “accepted”
I could reproduce that bug. With spaces as thousand separators, parsing fails.
-
Virgil Dupras April 6th, 2012 @ 06:42 PM
- Assigned user set to “Virgil Dupras”
-
Virgil Dupras April 6th, 2012 @ 06:51 PM
Oh well, it turns out that after more testing, space separator work fine, as long as there's only one of them. For example, "1 234" would work fine, but not "1 234 567". The thing is that the bug affects all space separators.
-
Virgil Dupras April 6th, 2012 @ 07:07 PM
Oh, no, I was all wrong. it's really the spaces that are the problem. It's just that sometimes, we get a
xa0character which is a non-breaking space. We just have to support those. -
Virgil Dupras April 6th, 2012 @ 09:50 PM
- State changed from “accepted” to “fixed”
(from [073178b99bd6]) [#316 state:fixed] Fixed bug where parsing would fail with non-breaking space in the string. https://bitbucket.org/hsoft/moneyguru/changeset/073178b99bd6/
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Virgil Dupras