[Mono-bugs] [Bug 78680][Wis] New - MWF MouseUp event handling problem

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Jun 21 05:21:56 EDT 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 daniel.baeyens at hispalinux.es.

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

--- shadow/78680	2006-06-21 05:21:56.000000000 -0400
+++ shadow/78680.tmp.31386	2006-06-21 05:21:56.000000000 -0400
@@ -0,0 +1,40 @@
+Bug#: 78680
+Product: Mono: Class Libraries
+Version: 1.0
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: peter at novonyx.com                            
+ReportedBy: daniel.baeyens at hispalinux.es               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: MWF MouseUp event handling problem
+
+I'm using mono 1.1.13 from Debian Unstable. I've found a bug with
+Windows.Forms events handling. 
+
+When you show a Dialog Window clicking on a widget, using the Click event,
+Windows.Forms raises the Window correctly and you can interact with the new
+window.
+
+If you show a Dialog Window clicking on a widget, but using the MouseUp
+event, system events get stuck, creating a new window on each click you
+make, until you close one of these windows with Alt+F4, then you recover
+the control.
+
+I've found this error looking a Visual Basic application, so I've created a
+small sample app which can be compiled with mbas. Visual Basic and mbas
+executables reproduce the same bug in the same way.
+
+I can't test it with the last version of mono and MWF right now, so maybe
+it could work correctly with that version
+
+The sample application can be compiled with:
+mbas -r:/usr/lib/mono/1.0/System.Windows.Forms.dll
+-r:/usr/lib/mono/1.0/System.Drawing.dll -m Form1 Form1.vb Form2.vb


More information about the mono-bugs mailing list