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. (Last updated on: November 16, 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback


Thread ID:





51758 Nov 13,2006 08:22 PM UTC Nov 14,2006 06:06 PM UTC General Discussion 1
Tags: General Discussion
Michael Enright
Asked On November 13, 2006 08:22 PM UTC

I am using version 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?

Purusothaman R [Syncfusion]
Replied On 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.



This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon