I am having a problem with the UltraDateTimeEditor when it comes to entering the year. When I entering 2010, as soon as I hit the 2 it sets the year to 2002 instead of letting me me enter the rest of the date. Then, being it puts the cursor at the end of the year, I start to to delete the 02 in order to entere, 10, as soon as I delete the second digit out of the year it refills in the year with 2020. The only way I have found for me to enter the year 2010 after 2002 has been filled it is first delete the last 2 and replace it with a zero (so that year is now 2000) and then use the arrow keys or the mouse to get to the second 0 and then delete it and replace it with 1.
I am running the lastest service release (Version 20103.2037). I have this when the MaskInput is set to both {date} and {LOC}mm/dd/yyyy
Hello,
Just checking if the latest reply helped you out and if you require any further assistance on the matter.
Sincerely,DimiDeveloper Support Engineer, MCPD Infragistics, Inc.www.infragistics.com/support
I'm still experiencing an issue with the year part of a date mask. No matter what mask I choose whether it is a mm/dd/yy,mm/dd/yyyy, or {date} the control tries to fill in the year with the first value I type in the year. For example, if I have the mask set to {date} and type 04/27/ and then type a 2 for 2011, the 2 triggers the control to set the year as 2002. Then if I hit backspace the year goes to _200 which is the expected behavior. Then I press backspace again it fills the year in with 2020. Thats not what I wanted. Now, hitting backspace repeatedly will only cause the year to toggle between 202 and 2020 What is going on here?
Hi, I have the same problem.. I have an UltraDateTimeEditor, and i do not have a business object binding, and i am using the ValueChanged Event to capture the date.. As soon as i enter 02/15/2, it triggers the event with 02/15/2002 value. Have you found a solution to this or can you please suggest any solution to this problem.
Thank you
Raj
I found the issue. I was binding to a business object and the DataSourceUpdateMode was set to OnPropertyChanged which was causing the undesired results. I switched the DataSourceUpdateMode to OnValidation and it works perfectly.