We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

DateTimePickerAdv_ValueChanged

I am using version 4.3.0.30 of the Syncfusion Essential Studio. I am curious about the DateTimePickerAdv ValueChanged event. If IsNullDate is set to true and you select a date, the ValueChanged event gets fired twice. The first time it seems to get fired because .IsNullDate is no longer true, but the .Value property hasn't been changed yet. The second time it gets fired the .Value has actually been changed. This makes the ValueChanged event difficult to work with. Wouldn't it make more sense for the IsNullDate property to have its own Change event?

1 Reply

PR Purusothaman R Syncfusion Team November 14, 2006 06:06 PM UTC

Hi Mike,

Thanks for bringing this issue to our notice.

I have created a Bug Report for this issue and here is the link for the same.
Defect #3032 - ValueChanged event triggers twice when isNullDate is True.

As per your suggestion, I have created a Feature Request for having a separate change event for isNullDate property.
Feature Request #1365 - Add a separate Change event for isNullDate Property.

Thanks for your interest in Syncfusion Products.

Regards,
Purusothaman.R

Loader.
Live Chat Icon For mobile
Up arrow icon