[Buster-Client] Forces use of primary monitor on multi monitor setup

[PBXg33k]

System

• OS name: Windows
• OS version: 10 Pro build 1809
• Browser name: Chrome
• Browser version: 74.0.3729.131 (Official Build) (64-bit)

Extension

• Extension version: 0.5.2
• User input simulation: yes
• Client app version: 0.2.0
• Client app installed successfully: yes

Bug description

When using User Input Simulation on multi monitor the client will get the browser's relative position from the correct monitor, but will place the cursor on the x and y offset of the OS's primary monitor.

IE: I have two monitors hooked up to my system, ML (left) and MR (right (primary)).
Chrome is open om ML and i trigger buster to do its magic. My cursor will move to MR, but will position itself relatively on the same position as where my browser/recaptcha dialog is, but it's on the wrong monitor.

Moving Chrome to MR will resolve this issue, but this forces me either to use a single monitor for Chrome, or drag it to MR whenever i want to let Buster do its thing

Logs
Browser:

N/A

Client app:

2019/05/14 10:20:36.323482 Starting client (version: 0.2.0)
2019/05/14 10:20:36.323482 Receiving message
2019/05/14 10:20:36.324483 Processing message
2019/05/14 10:20:36.324483 Command: ping
2019/05/14 10:20:36.324483 Sending response
2019/05/14 10:20:36.324483 Receiving message
2019/05/14 10:20:36.325483 Closing client

[dessant]

I'm planning to call operating system APIs directly instead of using robotgo, which has no multi-monitor support and lacks some features the client app will need for better input simulation.

[Bluscream]

I guess AHK would work aswell

[MrGeorgen]

I guess AHK would work aswell

only on windows

[mat926]

I am having a similar problem. If I connect another high res monitor and move the browser to the new monitor, buster will still use positions from the old monitor.