Key events don't get passed to RPD session

[chilimangoes]

In testing this with an RDP connection, the Key events don't seem to fire at all on a remote desktop. The ones in Dragonfly do fire, even if they often have timing/synchronicity issues when modifier keys (SHIFT, CTRL, etc) are used, so a good place to start is looking into the difference between how Dragonfly and the WindowsInput library trigger these keyboard events.

[Versatilus]

I haven't even looked at it yet so take this with the appropriate grain of salt, but I believe the difference is between using scancodes versus virtual keys. The Windows RDP client passes on scancodes, but it doesn't try to do anything intelligent with some of the messages Windows sends it.

…

On Mon, May 7, 2018 at 9:02 AM, Jacob Eggleston ***@***.***> wrote: In testing this with an RDP connection, the Key events don't seem to fire at all on a remote desktop. The ones in Dragonfly do fire, even if they often have timing/synchronicity issues when modifier keys (SHIFT, CTRL, etc) are used, so a good place to start is looking into the difference between how Dragonfly and the WindowsInput library trigger these keyboard events. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALpedYiIfK_Py_GFtIkut266Sp7FvZI4ks5twHAwgaJpZM4T1ONN> .

[chilimangoes]

Yeah. Shortly after posting this, I had done a quick Google search on using SendInput with RDP and one of the stackoverflow posts that I ran across mentioned needing to set the scan code on the INPUT struct. And sure enough, WindowsInput doesn't set the scan codes. So I think it should be a fairly straightforward fix, once I get some free time.