[Mono-bugs] [Bug 76026][Nor] Changed - BeginInvoke sample fails to work.

[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 peter at novonyx.com.

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

--- shadow/76026	2005-09-09 08:44:59.000000000 -0400
+++ shadow/76026.tmp.23684	2005-09-21 19:10:51.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 76026
 Product: Mono: Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Normal
 Component: Windows.Forms
 AssignedTo: peter at novonyx.com                            
 ReportedBy: miguel at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -28,6 +28,17 @@
 in (wrapper remoting-invoke-with-check)
 System.Windows.Forms.Control:BeginInvoke (System.Delegate)
 in <0x0005c> System.Windows.Forms.BeginInvokeDemo:UpdateLabel ()
 in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
 
 The clock never updates.
+
+------- Additional Comments From peter at novonyx.com  2005-09-21 19:10 -------
+This is a bug in the test app. It assumes that the label has been 
+created by the time the thread starts. On MS.Net that's the case 
+(because they're either slower creating the thread or faster creating 
+the control hierarchy). On Mono, the thread is running before the 
+windows are, up thus the crash. This was not seen when the test app 
+was originally written since we only recently added the exception to 
+BeginInvoke (after discovering on Win32 it with our nunit tests)
+
+I have updated the test app to wait until the handle is created.