I'm using RadControls for WinForms (2008.3 1204).
Assume the following: I have a DateTimePicker. MinDate and NullDate are both set to 1900/01/01. Now I change the MinDate property programmatically to 2009/01/01. In this case, the Value as well as the NullDate property will also be set to 2009/01/01. Furthermore, even if I set the NullDate back to 1900/01/01 after this it is not possible to set the DateTimePicker's value to the NullDate (either by Value=NullDate or by calling SetToNullDate() ) - because the value has to be between MinDate and MaxDate but the NullDate is not.
In my eyes this behaviour is senseless. First, the NullDate property should be completly independent from the MinDate - MaxDate range, to set one of them should not effect NullDate. Second: The DateTimePicker should accept the NullValue date as correct input, even if it is not between MinDate and MaxDate.
I think the condition for accepting a value should be
Or am I mistaken?
Assume the following: I have a DateTimePicker. MinDate and NullDate are both set to 1900/01/01. Now I change the MinDate property programmatically to 2009/01/01. In this case, the Value as well as the NullDate property will also be set to 2009/01/01. Furthermore, even if I set the NullDate back to 1900/01/01 after this it is not possible to set the DateTimePicker's value to the NullDate (either by Value=NullDate or by calling SetToNullDate() ) - because the value has to be between MinDate and MaxDate but the NullDate is not.
In my eyes this behaviour is senseless. First, the NullDate property should be completly independent from the MinDate - MaxDate range, to set one of them should not effect NullDate. Second: The DateTimePicker should accept the NullValue date as correct input, even if it is not between MinDate and MaxDate.
I think the condition for accepting a value should be
| Value == NullDate || |
| Value >= MinDate && Value <= MaxDate |
Or am I mistaken?
3 Answers, 1 is accepted
0
Hello renemt,
You are completely right. Please excuse us for the wrong behavior in RadDateTimePicker. I will do my best to fix the issue as soon as possible.
Thank you very much about the valuable feedback.
All the best,
Boyko Markov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
You are completely right. Please excuse us for the wrong behavior in RadDateTimePicker. I will do my best to fix the issue as soon as possible.
Thank you very much about the valuable feedback.
All the best,
Boyko Markov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
renemt
Top achievements
Rank 2
Rank 2
answered on 15 Jan 2009, 01:54 PM
Hi Boyko, hi telerik team,
thanks for the quick response, I look forward to the fix.
PS: How about some telerik points for my valuable feedback? I probably will purchase the whole control suite the next time so I could make good use of the points ;)
thanks for the quick response, I look forward to the fix.
PS: How about some telerik points for my valuable feedback? I probably will purchase the whole control suite the next time so I could make good use of the points ;)
0
Hi renemt,
I have just added 1000 more Telerik points to your account . Thank you one more time for the suggestion you gave me.
Kind regards,
Boyko Markov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
I have just added 1000 more Telerik points to your account . Thank you one more time for the suggestion you gave me.
Kind regards,
Boyko Markov
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.