[Mono-bugs] [Bug 75142][Maj] New - NumericUpDown & DomainUpDown do not display properly when Location is set before control is realized

[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 4lw0e0402 at sneakemail.com.

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

--- shadow/75142	2005-06-03 12:28:06.000000000 -0400
+++ shadow/75142.tmp.26026	2005-06-03 12:28:06.000000000 -0400
@@ -0,0 +1,36 @@
+Bug#: 75142
+Product: Mono: Class Libraries
+Version: unspecified
+OS: SUSE 9.1
+OS Details: only tested on SUSE 9.1, but probably happens elsewhere
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: Windows.Forms
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: 4lw0e0402 at sneakemail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: NumericUpDown & DomainUpDown do not display properly when Location is set before control is realized
+
+Description of Problem:
+  The controls derived from UpDownBase -- NumericUpDown and DomainUpDown
+  do not display properly if their Location is set immediately after
+  instantiation, before the control has been realized. The child controls
+  appear to be positioned incorrectly; when the control is subsequently
+  moved, the clipping error remains the same.
+
+Steps to reproduce the problem:
+1. Create a test form with Application.Run in its Main method.
+2. Within the constructor, instantiate a NumericUpDown or DomainUpDown
+   control, set its Location properly, and then add it to the Controls
+   collection.
+
+Actual Results:
+  The control is improperly clipped.
+
+Additional Information:
+  See attached test cases.