These mouse coordinates are relative to the active window so they shouldnt be clicking in the wrong places. The third parameter you can specify either Screen or Relative. I recorded a whole bunch of user interactions using autohotkey.When I play the script back, my mouse coordinates which are supposed to click somewhere, click somewhere else instead.

The second parameter specifies the coordinate mode will be for mouse coordinates. Hotkey Strokes are also available to quickly copy current coordinat. If you dont have the same x y coords each time, e.g. Simply run the script and it will show the current cursor coordinates in different CoordModes. Here’s a fun alternative to volume adjustment that lets you do it using your mouse wheel and the Alt key. Maybe set your SetTitleMatchMode to 2 because you are not using the exact correct WindowTitle text and in addition, if your window is like a Citrix XenApp window, you may have to deal with another criteria for identifying the target window ( see WinTitle in help).Īlso, you could try to identify and use the ClassNN (the classname and instance number of the control) or the name/text of the control, both of which can be determined via Window Spy. If you want coordinates to be relative to the active window, you need to use the CoordMode command at the top of your script. Hotkey Strokes are also available to quickly copy current coordinates - mouseposshow.ahk. CoordMode should not be used (unless for some other reason) as it doesn't impact the positioning of a ControlClick - which is always relative to the WindowTitle window you use.

Ahk mouse coordinates finder