inputsimulator
inputsimulator copied to clipboard
issue: doesn't work with apps that require scancodes, fix within
I was trying to use this with ZSNES and it wasn't working. I noticed after playing around with Spy++ that it only worked if you send the scanCode
my fix was: add to NativeMethods:
[DllImport("user32.dll")]
public static extern uint MapVirtualKey(uint uCode, uint uMapType);
add to InputBuilder::AddKeyDown() the following at the top:
ushort scanCode = (ushort)Native.NativeMethods.MapVirtualKey((uint)keyCode, 0);
and then below change Scan = 0 to Scan = scanCode
If you want I can submit a patch though it's really simple. However, there may be other places where you need to update it to use the scanCode
oh and you have to do it with AddKeyUp()
Thanks for that Dominic. I'll see if I can get an update through soon.
I'll have to check out ZSNES sometime too! ;)
On Mon, Jun 16, 2014 at 8:42 AM, Dominic Cerquetti <[email protected]
wrote:
I was trying to use this with ZSNES and it wasn't working. I noticed after playing around with Spy++ that it only worked if you send the scanCode
my fix was: add to NativeMethods:
[DllImport("user32.dll")] public static extern uint MapVirtualKey(uint uCode, uint uMapType);add to InputBuilder::AddKeyDown() the following at the top:
ushort scanCode = (ushort)Native.NativeMethods.MapVirtualKey((uint)
and then below change Scan = 0 to Scan = scanCode
If you want I can submit a patch though it's really simple. However, there may be other places where you need to update it to use the scanCode
— Reply to this email directly or view it on GitHub https://github.com/michaelnoonan/inputsimulator/issues/5.
sweet : )
I am also facing the same issue with citrix terminal . Key down and key up are not working. I see a pull request by @TChatzigiannakis which seems to address the issue. @michaelnoonan - Could you please look in to that PR #13 and accept the changes?
Having problems with this also, when it is getting accepted as a change??????
@RudiHansen You can use my fork where this issue is addressed.
Thanks @TChatzigiannakis that solved my problem
I think this was fixed, aside from LMENU #27