On Mon, Jul 15, 2013 at 7:02 PM, Alexandre Julliard julliard@winehq.org wrote:
This looks like a better approach, yes
Sorry, this approach doesn't work as I expected, further investigation show that posted messages would be processed before input messages, msdn confirms it:
--- quote --- If no filter is specified, messages are processed in the following order: Sent messages Posted messages Input (hardware) messages and system internal events Sent messages (again) WM_PAINT messages WM_TIMER messages --- quote ---
msdn also said: To retrieve input messages before posted messages, use the wMsgFilterMin and wMsgFilterMaxparameters.
However, even we can change the filter in our test, native Popup WndProc still receive posted messages before input message because it has its own message loop and we can't (and of cause we shouldn't) change it.
This situation run out of my head, I can't find any easy way to fix it, I doubt if there is any way better than the original patch (patch 97161, pending).
I'm open to any suggestion, thanks! If no better solution I hope patch 97161 is acceptable.
-- Regards, Qian Hong