comctl32: Make sure a WM_LBUTTONUP msg is dispatched while after a WM_LBUTTONDOWN msg
Alexandre Julliard
julliard at winehq.org
Thu May 12 04:45:51 CDT 2005
"Dmitry Timoshkov" <dmitry at baikal.ru> writes:
> Why WM_LBUTTONUP should be different from other kinds of messages?
> I.e. why all messages could not be passed to DispatchMessage? What
> if just move DispatchMessageW call right right after PeekMessageW?
Actually the whole function looks very suspicious, especially the busy
wait for a mouse message. I think this needs to be redone differently.
--
Alexandre Julliard
julliard at winehq.org
More information about the wine-devel
mailing list