Found the problem, not the fix.
message.c function PeekMessageW. It used to call FindWinToRepaint but that has been moved into the server. But FindWinToRepaint was able to return a window handle other than the original message window handle. 1. So what about the IsIconic line following it? Now it's testing the wrong handle. 2. (The real problem)PeekMessageW returns the message. Now the handle it returns is the unadulterated one, not the potential child. So what do we do about that? Get the server to return it?
Bill
-----Original Message----- From: Alexandre Julliard [mailto:julliard@winehq.com] Sent: Wednesday, November 14, 2001 1:29 PM To: wine-cvs@winehq.com Subject: wine/ dlls/user/message.c include/win.h server ...
ChangeSet ID: 1005773317852080273907632 CVSROOT: /opt/cvs-commit Module name: wine Changes by: julliard@wine2. 01/11/14 16:28:37
Modified files: dlls/user : message.c include : win.h server : queue.c user.h window.c windows : win.c
Log message: Moved WIN_FindWinToRepaint functionality to the server.
Patch: http://cvs.winehq.com/patch.py?id=1005773317852080273907632
Revision Changes Path 1.12 +0 -6 wine/dlls/user/message.c 1.64 +0 -1 wine/include/win.h 1.19 +3 -3 wine/server/queue.c 1.5 +1 -0 wine/server/user.h 1.10 +46 -1 wine/server/window.c 1.169 +0 -104 wine/windows/win.c
"Medland, Bill" Bill.Medland@accpac.com wrote in message news:8C156DB94BF414418FA2382DDCAEBA4A69C06F@603exc01.accpac.com...
Found the problem, not the fix.
<snip>
- (The real problem)PeekMessageW returns the message. Now the handle it
returns is the unadulterated one, not the potential child. So what do we
do
about that? Get the server to return it?
Sorry.
The problem is probably not in the code; it's in the way that it is used. It has demonstrated some sort of problem in the commctl code somewhere (at least I presume so since using the native commctl32 resolves the difficulty). I'll look into it.
Bill