how do "enter" the date value ? you type in the field ?
Max
ChronoForms developer...
ChronoForms v8 is out, do you have any suggestions? please let us know.
i put in date 8 febr 2023 it shows 8/2/2023
please put in the european date format dd-mm-yyyy
You can format dates with the syntax provided!
Max
ChronoForms developer...
ChronoForms v8 is out, do you have any suggestions? please let us know.
I have the same problem. I used the format DD.MM.YYYY, nonetheless it is changed to english format, when entering the inputfield.
I put "DD.MM.YYYY" in the display format and it shows "18.03.2023"
Max
ChronoForms developer...
ChronoForms v8 is out, do you have any suggestions? please let us know.
I think you didn't comprehend the problem (anyway like I have).
The (european) format and the value is right after entering via date picker. But when the user - after that - enters the input field (clicks on it), the format changes, so the value gets wrong.
what if you add a mask to the field to force a specific value format or make it read only ?
Max
ChronoForms developer...
ChronoForms v8 is out, do you have any suggestions? please let us know.
I think both, 'value mask' an 'read only' are options that are only available for 'text'-fields not for 'calendar'-fields.
Rollo71
posted Apr 5, 2023 at 14:43
I too had this problem.
You can make the field 'calendar' readonly by adding the 'HTML Tag Attribute' task in the INTERFACE and setting a custom HTML Attribute with the following values 'readonly true'.
In display mode remember to select 'Popup Calendar'.
This forces the user to use the calendar to select the date and does not allow him to enter it manually, thus avoiding the error encountered.
Thanks a lot. That works for me!
Gatsman
posted Apr 15, 2023 at 20:16
I also have this problem, it's good if this solution works for you and by all means use it but i don't think we should force the user to use only the popup calendar, some people for their own reasons (even accessibility issues) want and should be able to use the keyboard.
This should be addressed and solved at some point.