AD
Administrator
Syncfusion Team
April 4, 2005 12:18 PM
Hi Mike,
NumericUpDownExt is an extension of the .NET NumericUpDown. So since NumericUpDown does not support blank/null values, neither does NumericUpDownExt.
Regards,
Gregory Austin
Syncfusion Inc.
MI
Mike
April 5, 2005 02:07 PM
I just tested the original NumericUpDown control and it DOES leave the control blank after something has been entered and cleared. So this seems to be a feature of the Syncfusion''s extended control.
AD
Administrator
Syncfusion Team
April 5, 2005 02:33 PM
Hi Mike,
The NumericUpDown control can be cleared visually, but if you call NumericUpDown.Value, you''ll still get the old value. NumericUpDownExt just removes that ambiguity.
Regards,
Gregory Austin
Syncfusion Inc.
MI
Mike
April 6, 2005 01:15 PM
If the field Text property was left blank, I could check this property and mark my model that the field value was empty. The angle to look at it should be the usability for the user, not the ambiguity in the underlying component.
Please let me know if there is a way to programmatically suppress the behavior that Syncfusion has introduced.
AD
Administrator
Syncfusion Team
April 7, 2005 10:17 AM
Hi Mike,
I''ve looked into this some more and, while I still believe that NumericUpDown''s handling of blank values is a bug, I do see the value it adds. Therefore, I have requested that the ability to handle null values be added to NumericUpDownExt as Feature Request #131.
Regards,
Gregory Austin
Syncfusion Inc.