Everywhere the WIC calls Route_______ for slate events, you’ll tell it to use a specific user index, instead of the user index for the virtual user. In your case, user index 0, which is the user index for hardware cursor and mouse - though I expect the results won’t be great, since it will keep stealing focus from the viewport. The better way to do what you want, would probably be to write some C++ code that used the WIC to send all keyboard input the game receives, because otherwise you’re going right back to the problems caused by the system prior to the WIC. Also - there’s no way to know, “am i focused on an editable textbox” that concept doesn’t exist, there are widgets, and widgets have focus, what a widget chooses to do with its focus and any input is entirely up to the widget.