[RFC PATCH 4/6] user32: Remove __wine_send_input function.

[Alexandre Julliard]

Rémi Bernon <rbernon at codeweavers.com> writes:

> Regarding the hooks, I assumed that if we are processing input events,
> it means that the current thread is already in a message processing
> loop, so the hooks would eventually be processed if they belong to the
> same thread. Although maybe that would depend on the message filters?
>
> If they belong to another thread, it means that if for any reason that
> thread is not processing its messages, input events coming from the
> user would block the message loop instead of just being queued to the
> hooking thread. Maybe it's also something we expect?

Yes, the low-level hooks work basically like SendMessage, and block the
sender. There's a timeout in case the hooking thread is stuck.

-- 
Alexandre Julliard
julliard at winehq.org