id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
3884	MouseCoordMode, cursor moving and DPI unawareness	vadcx	Jon	"MouseMove documentation (and others) refer to MouseCoordMode which says:

 MouseCoordMode: Sets the way coords are used in the mouse functions,  either absolute coords or coords relative to the current active window:
 0 = relative coords to the active window
 '''1 = (default) absolute screen coordinates'''
 2 = relative coords to the client area of the active window

So the simple way to acquire absolute screen coordinates when needed:
1. Take a screenshot of the entire screen
2. Write down coordinates by navigating the picture

Let's say the mouse must be moved to 100,100 absolute.

{{{
MouseMove(100, 100)
}}}

If you didn't touch Windows' DPI settings (100%) then the cursor will move to 100,100. However if you set the DPI to 125% then the cursor moves to 125,125 and so on. Either the documentation must be clarified or the behaviour changed.

But it gets worse. Windows now has per-display DPI scaling. What is a script supposed to do in that case? This seems to be described in this [https://www.autohotkey.com/boards/viewtopic.php?t=97706 AHK-related thread] that seems to have the exact same problem as Au3."	Bug	assigned		AutoIt	3.3.16.0	None		mouse,move,coordinate,click,position,scale,dpi