I'm getting some unreliable behavior using Mouse.MoveTo().
I have two monitors on my Win10 PC. I have two encoders wired up to increment/decrement mouseX and mouseY vars. The encoders are working to ++ and -- the vars as designed. Serial output also verifies that mouseX and mouseY vars contain valid values.
But as I turn the encoder to move in the X axis, the mouse pointer doesn't always move.
Sometimes the pointer ends up on the primary monitor and other times it ends up on the secondary monitor.
I'm starting with mouseX=0 and mouseY=0 and the mouse pointer does go to that position to start on monitor two.
Can I force Mouse.MoveTo() to use the primary monitor only?
I have two monitors on my Win10 PC. I have two encoders wired up to increment/decrement mouseX and mouseY vars. The encoders are working to ++ and -- the vars as designed. Serial output also verifies that mouseX and mouseY vars contain valid values.
But as I turn the encoder to move in the X axis, the mouse pointer doesn't always move.
Sometimes the pointer ends up on the primary monitor and other times it ends up on the secondary monitor.
I'm starting with mouseX=0 and mouseY=0 and the mouse pointer does go to that position to start on monitor two.
Can I force Mouse.MoveTo() to use the primary monitor only?