Issue with pause key events about controllerbuddy HOT 3 CLOSED

OSK uses virtual key codes instead of scan codes:

from controllerbuddy.

Next up: compare with the events generated by a physical keyboard

from controllerbuddy.

From https://github.com/chromium/chromium/blob/99314be8152e688bafbbf9a615536bdbb289ea87/remoting/host/keyboard_layout_monitor_win.cc#L179

// The USB keyboard driver translates NumLock to the scancode 0x45, but it
// is delivered to applications as 0xE045. Meanwhile, Pause is translated
// to the scancode sequence 0xE1 0x1D 0x45 0xE1 0x9D 0xC5, but is delivered
// to applications as a plain 0x45.
//
// Injecting 0x45 using SendInput does get interpreted by Windows as
// VK_NUMLOCK, but is not translated to 0xE045 before being delivered to
// applications as it is with a physical keyboard. As a result, Chrome (for
// example) reports a key value of "NumLock" but a code value of "Pause".
//
// Injecting 0xE045, on the otherhand, does not get interpreted as
// VK_NUMLOCK, so Chrome sees reports a code value of "NumLock", but a key
// value of "Unidentified".
//
// I have not been able to determine any way to use SendInput to inject an
// event that Windows interprets as VK_PAUSE.

from controllerbuddy.