Greetings,
We are having difficulty getting the kendoui datepicker working under what we consider to be some fairly common use cases.
Example 1:
Easily visible via the sample: http://demos.telerik.com/kendo-ui/web/datepicker/events.html
Consider a requirement where this field is optional, but if filled in must parse out and be a legitimate date. Currently if I enter "asdfasdf" or even something as innocent as "25/5/2012" (consider a non-us user who is used to dd/mm/yyyy) then the changed event is never fired. I thus have no opportunity to warn the user that the date they have entered is invalid.
Example 2:
Let's say I set a maximum date of todays date on the control. Now when I click the calendar, it properly disallows selection of a future date. However, what I can do is go in and type in any date I want. If a date in the future is inputted, the control determines null as the value and again, since the initial value was null as well the change event is never raised, and there is no way to provide UI validation in an MVVM scenario.
Desired behavior
The easiest change here probably would be to simply give us an option to have the textbox get cleared out when the control loses focus if the date is null that way at least what the user sees in the control will match what the control is reporting as its' value.
A good example of this is the multiselect box. If you type gyberish into it and tab out, it wipes out the invalid value. Why does the datepicker need to retain its invalid data?
Otherwise, we need some way to be notified via event not only when the underlying date value has changed, but also when the text changes if we are to jump through these hoops ourselves (manually parse the text according to configured formats, clear out the value if needed, etc).
We are having difficulty getting the kendoui datepicker working under what we consider to be some fairly common use cases.
Example 1:
Easily visible via the sample: http://demos.telerik.com/kendo-ui/web/datepicker/events.html
Consider a requirement where this field is optional, but if filled in must parse out and be a legitimate date. Currently if I enter "asdfasdf" or even something as innocent as "25/5/2012" (consider a non-us user who is used to dd/mm/yyyy) then the changed event is never fired. I thus have no opportunity to warn the user that the date they have entered is invalid.
Example 2:
Let's say I set a maximum date of todays date on the control. Now when I click the calendar, it properly disallows selection of a future date. However, what I can do is go in and type in any date I want. If a date in the future is inputted, the control determines null as the value and again, since the initial value was null as well the change event is never raised, and there is no way to provide UI validation in an MVVM scenario.
Desired behavior
The easiest change here probably would be to simply give us an option to have the textbox get cleared out when the control loses focus if the date is null that way at least what the user sees in the control will match what the control is reporting as its' value.
A good example of this is the multiselect box. If you type gyberish into it and tab out, it wipes out the invalid value. Why does the datepicker need to retain its invalid data?
Otherwise, we need some way to be notified via event not only when the underlying date value has changed, but also when the text changes if we are to jump through these hoops ourselves (manually parse the text according to configured formats, clear out the value if needed, etc).