On 9/14/21 6:38 PM, Piotr Caban wrote:
I'm attaching a simple application that may be used to observe the problem. The application creates a window and waits for WM_KEYDOWN message. It deadlocks without the patch. Unfortunately there's no way of testing it without the ability to generate non-injected hardware messages. I can add an interactive test if it's preferred.
Thanks, Piotr
With an HID test signed driver, like I'm currently adding for dinput testing, we could test mouse and keyboard input without going through SendInput / kbd_event / mouse_event.