Hi,
I’m trying to debug an app that uses the RemoteControlMBS.WinPressKey function.
In a small sample, I have the following code running on Windows, after a delay of 2 seconds (so I can quickly switch to a text field to see the result):
call RemoteControlMBS.WinPressKey 11,98,True
call RemoteControlMBS.WinPressKey 11,98,False
This should produce pressing the “b” key (ascii=98, physical key=11), but does actually simulate “2” and I can’t figure out why: “2” has nothing to do with either 98 nor 11. I also tried swapping the parameters in case I had it backward, and it made no visible character.
As this is a simple example which shouldn’t fail (e.g. “b” is always at the same position regardless of the layout), I’m reporting my finding, hoping someone could either try, tell me where I’m wrong, or pinpoint a bug in the MBS plugins.
3 posts - 2 participants