[Mono-bugs] [Bug 80830][Wis] New - DateTimePicker - Text property bug

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by xmak at studioartlan.com.

http://bugzilla.ximian.com/show_bug.cgi?id=80830

--- shadow/80830	2007-02-13 11:33:02.000000000 -0500
+++ shadow/80830.tmp.25376	2007-02-13 11:33:02.000000000 -0500
@@ -0,0 +1,62 @@
+Bug#: 80830
+Product: Mono: Class Libraries
+Version: 1.2
+OS: Windows XP
+OS Details: Windows XP SP2
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: toshok at ximian.com                            
+ReportedBy: xmak at studioartlan.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: DateTimePicker - Text property bug
+
+Description of Problem:
+
+When you assign to a Text property of a DateTimePicker object, a string
+value that is not a valid date according to the object's Format, mono just
+breaks without any error message.
+
+
+Steps to reproduce the problem:
+
+1. Create a new Windows.Forms application
+2. Create a in the main form:
+- a DateTimePicker dtpTest
+- a Button btnTest
+3. In the OnClick event handler of the btnTest write this code:
+
+dtpTest.Text = ""
+
+(or any other code that assings an invalid datetime string to the Text property
+
+4. Execute the program and click the button on the form
+
+
+Actual Results:
+
+Mono crashes without any warning.
+
+
+Expected Results:
+
+The expected result is to leave the DateTimePicker's Text and Value intact,
+since this is how the program behaves when I run it on Windows regulary,
+without mono.
+
+
+How often does this happen? 
+
+Always.
+
+Additional Information:
+
+Also, the DateTimePicker doesn't respect the current language and regional
+settings (or current culture), it always displays the date in US language.
+When I run the program regulary, without mono, the current culture is
+respected.  But this is maybe an issue for another bug?