 |
This works fine in 1.92. If alternate values are needed you can use a preg filter on this question type. That won't prevent entry of invalid characters, but will set the background color of the field to red if it doesn't meet the validation criteria. |
 |
1.92RC3 released |
 |
I can not switch to a newer version right now, I have several surveys active at the moment. so I just have to ask. Does it now behave like it is meant to or do I have to add something additional to my question (like some kind of regex)? In my opinion it would be better if questions of similar kind would behave the same. It is not obvious for the user if the decimal seperator of "the normal" keyboard does not work but the one of the numbers block does. And if I choose a locale like e.g. German for the survey I think it would be great if all numbers fields would only accept numbers in the locale specific format. Otherwise it is not user friendly and easy to use. Thanks a lot for looking into this. And sorry for asking again. |
|
|
The core problem here is the use (in 1.91+ and beyond) of an onkeypress event to only allow numbers to be entered in the field. Perhaps we should move away from that and use regular expression validation whenever people select numbers only. Then we could have different regex for different countries, making it easier to use commas or spaces as thousands and/or decimal separators when needed. This would also allow us to support negative numbers, which currently don't work for many numbers-only entries. |
|
|
on second look, the core problem is with the multi_set() function. The onkeypress() function is allowing commas. Either way, however, you can still enter invalid numbers. Incorporating regex-based validation could fix that. |
|
|
You are right, it would be possible to use regex-validation for numbers. I am using short text question type combined with regex for numberformat with thousands seperator or negative numbers. But I have made the experience that survey participants don't really like that and they ususally prefer fields where they only can enter things that are allowed and they don't have to find the question on the page where something is missing and/or something is in an incorrect format. In the meantime I use inputmask for things like that. But I have not tried to use the code for matrix (text) instead of "only numbers" option |
|
|
Fixed with patch https://github.com/LimeSurvey/LimeSurvey/commit/d71ff2dce798a695614eff9cf807f98b2ae5dfdb |
|
|
Thank you, as soon as I will have time, I will test the patch |
|
|
Actually, it will be available in 1.92 RC5, which, with luck, will be released today. |
|
|
1.92RC5 release |
- Anonymous
