[Mono-bugs] [Bug 78718][Nor] New - Form: Setting Form.MdiParent to null when the container is not null crashes.

[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 unserkonig at gmail.com.

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

--- shadow/78718	2006-06-27 15:21:34.000000000 -0400
+++ shadow/78718.tmp.19660	2006-06-27 15:21:34.000000000 -0400
@@ -0,0 +1,32 @@
+Bug#: 78718
+Product: Mono: Class Libraries
+Version: 1.1
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Windows.Forms
+AssignedTo: peter at novonyx.com                            
+ReportedBy: unserkonig at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Form: Setting Form.MdiParent to null when the container is not null crashes.
+
+Setting Form.MdiParent to null in the mdi child, after both container and
+child have been displayed in the screen, causes a NullReferenceException.
+The right behavior is to have the mdi child form separated from the mdi
+container form.
+
+Steps to reproduce the problem:
+1. Compile the sample.
+2. Run it and click on the "Click me" button.
+
+Actual Results:
+A NullReferenceException is thrown.
+
+Expected Results:
+The child mdi form should be separated from the mdi container form.