[Mono-bugs] [Bug 80372][Min] New - MouseMove must be fired after MouseDown/MouseUp

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Dec 26 23:59:07 EST 2006

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 everaldo at simios.org.


--- shadow/80372	2006-12-26 23:59:07.000000000 -0500
+++ shadow/80372.tmp.10049	2006-12-26 23:59:07.000000000 -0500
@@ -0,0 +1,36 @@
+Bug#: 80372
+Product: Mono: Class Libraries
+Version: 1.2
+OS Details: 
+Status: NEW   
+Priority: Minor
+Component: Windows.Forms
+AssignedTo: toshok at ximian.com                            
+ReportedBy: everaldo at simios.org               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: MouseMove must be fired after MouseDown/MouseUp
+In Win32 after MouseDown/MouseUp an MouseMove must be fired
+Steps to reproduce the problem:
+Create any program that assign a event MouseDown, MouseUp and MouseMove to
+any System.Windows.Forms.Control derived control. In Win32 an MouseMove is
+fired after MouseDown, MouseUp and in Mono it does not happen.
+Actual Results:
+MouseMove dont fired
+Expected Results:
+MouseMove must be fired
+How often does this happen? 
+Always for all controls derived from Control.

More information about the mono-bugs mailing list