Actually send scancodes after figuring them out

[PureSpider]

If we do all this work to figure out associated scancodes for virtual keys, we should use them to actually send keystrokes as such.

[oktapodia]

Thank you for your PR @PureSpider and sorry for the delay, I am struggling to understand exactly what this PR is doing, can you please explain?

[PureSpider]

Sure:

• For the method to actually send scan codes, the KEYEVENTF_SCANCODE flag needs to be set. If it is not, the virtual keys method and the associated value is used instead, while the scan code value is ignored.
• Modifiers and keys should be pressed and released in a more natural order: modifier press, then key press, then key release, then modifier release. Some applications detect shortcuts on the key up instead of the key down event.
• The time between modifier press and key press should never be zero - some applications struggle to recognize the events correctly if it is. Same goes for key release.

Let me know if you have further questions

[oktapodia]

Sounds amazing! Thank you! I'll merge it after Appveyor finish its work

[oktapodia]

Thank you for your PR!