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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80546 --- shadow/80546 2007-01-25 22:09:36.000000000 -0500 +++ shadow/80546.tmp.13583 2007-01-26 04:34:22.000000000 -0500 @@ -99,6 +99,22 @@ 4. no background change, but the cursor changes to the busy cursor. This is due to the way we handle WM_SETCURSOR. It calls XplatUI.SetCursor which causes X to associate the cursor with that window. But we never clear it. There's got to be some other message, or some other logic we're missing. + +------- Additional Comments From [EMAIL PROTECTED] 2007-01-26 04:34 ------- +I can reproduce the issue with the steps outlined in my repro. When I +said "On step 5 of tabs #2 and #3 our behavior differs", I didn't +mean to say that you only need to execute that step. + +On MS, I get the exact results described on tabs #2 and #3 while on +Mono I do not. + +As Chris mentioned, the mouse cursor changes even if another control +(in this case, the form) still has capture control. + +Also, when you release the mouse capture while over the child area +and do not move the mouse, then the MouseEnter event does not fire, +and hence neither the mouse cursor nor the background color of the +child area will change. See tab #3 for this. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
