[Mono-bugs] [Bug 80877][Wis] New - DrawReversible Stuff Still Buggy

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Feb 16 19:05:42 EST 2007

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 eric at rengeo.com.


--- shadow/80877	2007-02-16 19:05:42.000000000 -0500
+++ shadow/80877.tmp.5474	2007-02-16 19:05:42.000000000 -0500
@@ -0,0 +1,62 @@
+Bug#: 80877
+Product: Mono: Class Libraries
+Version: 1.2
+OS Details: SuSE 10.1
+Status: NEW   
+Priority: Wishlist
+Component: Windows.Forms
+AssignedTo: toshok at ximian.com                            
+ReportedBy: eric at rengeo.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: DrawReversible Stuff Still Buggy
+Description of Problem:
+DrawReversibleLine, Frame, FillReversibleRectangle, etc don't draw
+correctly when the draw is in an embedded control (I think).
+Steps to reproduce the problem:
+1. Create a userControl, with a mouseMove event that draws lines
+2. Put that control in a Form Container.
+3. Move Mouse in control to trigger event.
+1. Compile attached test case with:
+mcs -r:System.Windows.Forms -r:System.Drawing -r:System.Data Form1.cs
+2. Run the test case
+mono Form1.exe
+3.  No reversible line drawing is done at all.
+Actual Results:
+No reversible lines appear anywhere.
+Expected Results:
+Reversible lines should appear.  Coordinates of the mouse in each control
+should be calculated to screen coordinates, and a crosshair of size 10
+should be drawn using DrawReversibleLine().  These crosshairs should be
+drawn on every other control if the checkbox is checked.  If it's not
+checked, it only draws on the control the mouse is in.  The clear button
+just sends an invalidate message.
+How often does this happen? 
+Additional Information:
+Could it be that Mono is sending extra invalidates on child controls,
+causing the drawn lines to be overwritten immediately?  The DrawReversible
+functions definately *are* getting called after examining the results of
+the --trace option.  Ill attach a snipped output of that too.

More information about the mono-bugs mailing list