When typing in a date in the UltraDateTimeEditor the value changed event is firing as soon as you type in the first digit of the year. This causes the date to be set in the control. I tested against Net Advantage 2009.1 and also the Service Release 2039.
To test create a winform drag a date time editor onto the form subscribe to the value changed event and put a break point on the event. Run app and type in a date. As soon as you type the first digit for the year part the event fires and sets the date.
This is only a problem if you subscribe to the value changed event.
Hi Dimitris,
It looks like we started a support case on this, but the original poster was never able to tell us how to reproduce the issue. So since we cannot duplicate the problem, we haven't been able to look into it.
Are you able to duplicate this in a small sample project? If so, please post it here and we will check it out.
Is there anything new in this problem?
Hm. I just tested this out and it looks like I was wrong. DateTime.Parse("1") does not return a valid date, it raises an exception.
So if this behavior changed from a previous version it must have been as part of a bug fix and it may not have been intentional. I'll forward this thread over to Infragistics Developer Support so they can check it out.
Are you stating that the ValueChangedEvent should fire on the first digit I type in?
Currently it fires on the first digit of the year portion. Does that happen because the when I enter in the first digit of year the date.parse is successful?
Subscribing to the ValueChangedEvent will aways set the year to 2000 to 2009 if typing in a date.
This was not the behavior of this control in the 2008 .net 2.0 version.
We recently upgraded to 2009 controls and this has caused breaking changes at RunTime in our application.
I can change from using the ValueChangedEvent to AfterExitEditMode and all is fine.