Inconsistency of parsed values

[Patrick]

Hello,
if I enter 0:5 in the time picker, a time of 00:05 (5 minutes) is selected.
If I enter :5 in the time picker a time of 05:00 (5 hours) si selected.
The parser ignores the ":" if it has no number at the front.
Patrick

[Konstantina]

Hi Patrick,

Thank you for your feedback.

We have planned a major refactoring of the current parsing of the RadDateTimePicker control, and we will consider this issue when implementing it.

If you have further suggestions or questions please let us know.

Regards,
Konstantina
Telerik

[Patrick]

Hi Konstantina,
At the same time, make that, if I enter 19.12.99 as a date, it takes 19.12.1999 and not 19.12.2099.
Or, at least let us select how it should work.
Patrick

[Konstantina]

Hello Patrick,

Thank you once again for you remark.

This will definitely be changed. However, I want to ask you, how do you expect the year to be autocompleted, when you enter just 1 or 2 digits for it - I mean already 4 digits are entered for the day and month and only 2 or 3 for the year?
For example: entered 220679 -> which year do you expect to be parsed for the date of 22nd of June?

Regards,
Konstantina
Telerik

[Patrick]

Konstantina,
in Windows, there is an option in the control panel where you can specify how a two-digit year should be interpreted. That can be a good default value for the control.
But, in a LOB application, the application writer know the meaning of the entered date and can provide a more precise use for a 2 digits year. For example, if I know the date represents a birthdate, I can define that the range for a 2 dgits year in 1914 to 2013. If the date is for a future event, I want the range to be 2013 to 2112.
So I think the best solution would be to have a dependency property to define the range of dates to take into account for an instance of the DateTimePicker control. The default value of this property would be the default value specified in Windows. And we can fine tune the value for a specific control, depending on its specific content.
Patrick

[Konstantina]

Patrick,

Thank you for your suggestions, they sound reasonable.
We will consider them and implement the most intuitive one.

Your opinion matter to us, thank you.

Regards,
Konstantina
Telerik