It looks like I can set the MinDate and MaxDate of UltraDateTimeEditor. It will validate the value being assigned to it programmatically using the range; however, the editor and the dropdown are still acting using the default behavior.
I set the MinDate to 1/1/1950 and MaxDate to 12/31/2049. The control still only lets me type 12/31/29 and the dropdown only goes up to 12/31/2029. Is this expected?
Version 11.2.
EDIT: Somehow the MaskInput of mm/dd/yy is affecting the behavior. Without the MaskInput, the control behaves as expected.
We are still deciding on what to do. We are just going to suggest changing the OS century setting for our customers that need date beyond 2029 for the meantime.
Hi,
Are you fine with the four digit for year in the input mask? Is there anything else I can do for you?
As I explained above, it's because you are using a 2-digit year. If you have a mask with a 2-digit year and you enter:
"1/1/30", then the DotNet Framework will interpret this as 1/1/1930. This is before your MinValue, so it's not valid.
The solution is to use a 4-digit year in your mask.
Sorry, I wasn't clear about the 2029. I mean if you set the MaxDate to 12/31/2049, it is still only allowing you to type up to 2029 when the year input mask is only 2 digits. The control seems to work as expected when there is no input mask.
I'm using a mask with only two digits. I'm just not so sure why the control is not respecting the MinDate and MaxDate. It validates the control using the range, but the textbox and the dropdown will still only display up to 2029.
Something is not right, I get an Exception when I have the MaxDate set, and I press Page Down on Dec. 2029 dropdown view.