[PATCH] user32: Add a timeout when sending WM_WINE_DESTROYWINDOW
Andrew Eikum
aeikum at codeweavers.com
Fri Feb 23 09:13:07 CST 2018
On Fri, Feb 23, 2018 at 03:54:14PM +0100, Alexandre Julliard wrote:
> I don't think we want to simply ignore the failure and keep child
> windows alive when their parent is gone. Probably the sequence could be
> changed so that WM_WINE_DESTROYWINDOW is sent first, and WM_DESTROY is
> sent in the context of the target thread.
>
Makes sense, I can experiment with that. Thanks.
Andrew
More information about the wine-devel
mailing list