Juris Smotrovs <[EMAIL PROTECTED]> writes: > The defwinproc mismatch itself appears > because, after solving the WM_SIZE issue, this message -- > correctly -- is sent, so the actual message queue shifts > relative to the expected message queue, and -- due to > some messages still missing -- three expected defwinproc > messages coincide with three actual non-defwinproc messages > which are expected later-on. Thus this failure is actually > not about messages sent from incorrect place, but simply > about missing messages which is a very typical failure > among the todo tests.
Ah OK, I get it now. Thanks, I'll put it in. -- Alexandre Julliard [EMAIL PROTECTED]
