edit.c: WM_MOUSEACTIVATE

Ulrich Czekalla ulrich.czekalla at utoronto.ca
Thu Apr 28 13:25:43 CDT 2005


I don't see any evidence that the edit control always returns MA_ACTIVATE
in response to a WM_MOUSEACTIVATE message. In fact, when sending it a
MA_ACTIVATE it seems to get processed by the default window proc and
therefore makes it way up the window tree. 

This patches fixes an activation bug in my application that expects to see
the WM_MOUSEACTIVATE in one of the parent windows of the edit control.


ChangeLog:
    Ulrich Czekalla <ulrich at codeweavers.com>
    Let the default windproc handle WM_MOUSEACTIVATE
-------------- next part --------------
Index: dlls/user/edit.c
===================================================================
RCS file: /cvstrees/crossover/office/wine/dlls/user/edit.c,v
retrieving revision 1.16
diff -u -p -r1.16 edit.c
--- dlls/user/edit.c	19 Apr 2005 17:35:36 -0000	1.16
+++ dlls/user/edit.c	28 Apr 2005 18:19:10 -0000
@@ -953,10 +953,6 @@ static LRESULT WINAPI EditWndProc_common
   		result = EDIT_WM_MButtonDown(es);
 		break;
 
-	case WM_MOUSEACTIVATE:
-		result = MA_ACTIVATE;
-		break;
-
 	case WM_MOUSEMOVE:
 		result = EDIT_WM_MouseMove(es, (short)LOWORD(lParam), (short)HIWORD(lParam));
 		break;


More information about the wine-patches mailing list