[Bug 434] Changed - Mouse button don't get released (Macromedia Flash 5.0)
wine-bugs at winehq.com
wine-bugs at winehq.com
Wed Apr 10 14:27:55 CDT 2002
http://bugs.codeweavers.com/show_bug.cgi?id=434
*** shadow/434 Wed Apr 10 12:14:12 2002
--- shadow/434.tmp.27852 Wed Apr 10 14:27:55 2002
***************
*** 378,380 ****
--- 378,423 ----
Hope to see this solved soon - I would love to be able to use these programs
with wine. Cheers =)
+
+ ------- Additional Comments From ivanovich at menta.net 2002-04-10 14:27 -------
+ >I assume it was Alexandre's patch that moved functions into the wine server,
+ >but I wasn't able to confirm it for sure (intermediate patches wouldn't
+ >compile for me)
+
+ Some time before i got a current wine cvs repository and updated and recompiled
+ wine and tested if the bug was present for every patch in the day in which wine
+ breaks, the patch http://cvs.winehq.com/patch.py?id=992978202334525382146239
+ "Moved hardware message queue handling to the server." is for sure the one which
+ causes the bug.
+
+ Did you talked with Alexandre about the bug?
+
+ About what Rein Klazes asked:
+ "You could try to look for the WM_CAPTURECHANGED messages. This message
+ is sent when a window looses the capture. If I understand you correctly you
+ think that your problem is that this doesn't happen, while in the old situation
+ it did. If you have access to the spy++
+ program, run it under windows and compare the messages between wine
+ and windows."
+
+ the WM_CAPTURECHANGED msgs appear in user32 right?
+ i tried getting the debug with this:
+ wine --debugmsg +relay=user32-relay=GetSysColor flash.exe &> winedebugoutput.txt
+
+ the last lines from it are:
+ 080714f8:Call window proc 0x406cf3c0
+ (hwnd=00010024,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000)
+ 080714f8:Ret window proc 0x406cf3c0
+ (hwnd=00010024,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) retval=00020021
+ 080714f8:Call window proc 0x759b5a
+ (hwnd=00020022,msg=WM_LBUTTONDOWN,wp=00000001,lp=004801ba)
+ fixme:imm:ImmGetContext (0x00020022): stub
+ -- 100% cpu , ctrl+c --
+
+ but i dont have spy++ (nor i know what is it)...
+
+ maybe looking at the output of the working version of wine with this same debug
+ options we can locate the error? i think i can do it tonight
+
+ btw, any idea what the last "fixme" line means? and the number 20022? (note that
+ retval from WM_MDIGETACTIVE is 20021)
\ No newline at end of file
More information about the wine-bugs
mailing list