Jump to content

Recommended Posts

So from all my research from this forum, I've came up with pretty much the same algorithm written many different ways -- all are yielding the same, yet wrong, answer.

In My PC the x spot where i want to click is in the 400 pixel.

In another PC is not in the same position because the resolution change.

So i do some maths. First, i think.. The porcentage of the desktopwidth that tells me where is the spot

If desktopwidth is the 100% then 400 will be the xx%

$xPercent = 400 * 100 / @DesktopWidth

so i grab that number and start using that number instead of 400 in the following way

$x = xPercent * @DesktopWidth / 100

I hope you understand my way to do it.

ToolTip( "Waiting for you to click the mouse to set initial position", @DesktopWidth / 2, 50, "Awaiting input.", 1, 2 )

;Set mouse click position

While 1

If _IsPressed( 01 ) Then

$MP = MouseGetPos()

$RelativePOSX = $MP[0] / @DesktopWidth

$RelativePOSY = $MP[1] / @DesktopHeight






Func CoordSwitch($X, $Y, $W, $H) ; $W, $H - Original

; MouseClick("Left", @DesktopWidth / $W * $X, @DesktopHeight / $H * $Y, 1)

MsgBox(0, 'Coord', 'x = '&@DesktopWidth / $W * $X &@CRLF& 'y = '&@DesktopHeight / $H * $Y)


My example:

I want to click on a certain button with MouseClick. It is located at 885, 183 (we will just use the x coord for demonstration) with the resolution of 1440x900. I want to be able to click on that same button (it's very small) with a 1280x720 resolution as well. So, I plugged in 885 in any of those 3 equations and they ALL result in 785 for the answer. The problem? I used Au3Info and that coordinate actually resides on 772 (x).

Why such the big difference? I do realize there are aspect ratios, but I have not seen them demonstrated in ANY of the threads I found - and people claimed these conversions were working for them... (1440x900 = 16:10 and 1280x720 = 16:9 ratios)

Any ideas? o.o


Link to post
Share on other sites

I want to click on a certain button with MouseClick

Its not the efficient way

Try with ControlClick and use Autoit Window Info tool to find the Information required

Then no problem should reside regarding resolution or the position of the Button


Phoenix XL

Edited by PhoenixXL

My code:

PredictText: Predict Text of an Edit Control Like Scite. Remote Gmail: Execute your Scripts through Gmail. StringRegExp:Share and learn RegExp.

Run As System: A command line wrapper around PSEXEC.exe to execute your apps scripts as System (LSA). Database: An easier approach for _SQ_LITE beginners.

MathsEx: A UDF for Fractions and LCM, GCF/HCF. FloatingText: An UDF for make your text floating. Clipboard Extendor: A clipboard monitoring tool. 

Custom ScrollBar: Scroll Bar made with GDI+, user can use bitmaps instead. RestrictEdit_SRE: Restrict text in an Edit Control through a Regular Expression.

Link to post
Share on other sites

I don't get it, if a gui is 400 x 400 pixels

It is 400 x 400 pixels at 1440x900 res and it is 400 x 400 pixels 1280x720 res.

Please use MouseCoordMode Option, or provide some kind of believable scenario where that does not work.

AutoIt Absolute Beginners    Require a serial    Pause Script    Video Tutorials by Morthawt   ipify 

Monkey's are, like, natures humans.

Link to post
Share on other sites

I'm not saying the GUI isn't the same - it would be. However - MouseClicks are not. And when you can't record the coordinates via the window (controlclick coords), you must use absolute coords so MouseCoordMode doesn't apply.

My example is above and you can simply test it by changing your screen resolution and try double clicking on a program on your desktop (leave the script as-is when changing res.). It won't click on the same program.

Link to post
Share on other sites

The formula works perfectly, it'll click on the exact same physical spot on your monitor, regardless of the resolution. Put a big greasy thumbprint on the target spot of your monitor and in 5 different resolutions the mouseclick will hit the spot.

I think you're expecting webpages or GUI's to be simply proportionally stretched or zoomed when you change resolutions. I've found that not to be the case. I believe everything is redrawn with different fonts, control sizes, spacings, etc. There's no guarantee that a button 20% from the left margin of the screen in a 1280 resolution will be redrawn exactly 20% from the left edge in other resolutions.

If you can't reference controls directly, then you'd need to maintain a table of coordinates, and use the appropriate set of numbers depending on the users resolution.


Edited by Spiff59
Link to post
Share on other sites

Ok, I get what you're saying here. So you mean there is no efficient way to convert a x-coordinate at 885 (1440x900 res) to a coord on a 1280x720?

Could the aspect ratio be the cause of the slight difference between the answer to the equation (785 x-coord) and the actual answer (772)? Would there be a way to somehow run that aspect ratio into that algorithm above?

Link to post
Share on other sites

If the Mona Lisa were your desktop background and you wanted to poke her in the eye with a mouseclick, I think the formula would work on all resolutions, because you are evenly stretching or shrinking the image proportionately to match the desktop resolution. The image is a single entity being resized.

I had no luck applying that principle in the past to system controls, html, and the like that are a bunch of seperate entities and seem to be sized, placed and spaced however Windows wants under different resolutions. I was suggesting you document the locations of each control under each supported resolution, and hardcode them in the program (or read them from a flat file if you prefer)

Global $aResolutions[3] = ["1024x768","1280x1024","1440x900"]
Global $aSaveButtonCoords[3][2] = [[?,?],[772,?],[885,183]]

; determine resolution at program start
$CurrRes = @DesktopWidth & "x" & @DesktopHeight
For $x = 0 to 2
    If $CurrRes = $aResolutions[$x] Then
        $CurrRes = $x
If $x = 3 Then
    MsgBox(0,"","Unknown resolution!")

; later processing

Edit: It's certainly not as clean a solution as direct interaction with the controls, or even a bunch of Send("{TAB}{TAB}{ENTER}") statements, but it may be a way that works?

Edited by Spiff59
Link to post
Share on other sites

Yeah, that surely WILL work, but I was hoping to avoid that. I have programmed it in 1440x900 already, I was just hoping I could find a way to convert all those coordinates [properly] so I didn't have to go back and record 600 lines of code again (a bit sarcasm, but you understand the frustration of having to redo something that's already done -- isn't that the point of automation lol?)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By TheDcoder
      Hello, it has been a long time since I have posted here
      I am working on an AutoIt project where I need to enable to user to interactively choose any point or coordinate on the screen... something like a big overlay where the user can click anywhere on the screen to select that point. @UEZ's screenshot tool may have something similar to what I need:
      I just checked the source code for the tool and I see that the Mark_Area function has a part in selecting the area to screenshot, I tried to figure out how it works but it is simply too complex and long...
      So I was wondering if there were any examples of interactively selecting points on a screen? Maybe an UDF that I can just use in my script to make the whole thing a matter of adding few lines
      Thank you for the replies in advance!
    • By tentacole
      This is my first post, so I apologize if this is in the wrong place. 
      I've created a while loop to click in a certain area of an application, and have the y axis change at the end of each loop. My loop continues to click at x:27, x:10, even though the $y is adding 15 at the end of each loop. I did a Send($x) and Send($y) into a Notepad to see if the $y had changed after each loop, and the 15 was being added to $y each loop. (If this makes sense)
      I'm unsure where I'm going wrong, and would be extremely grateful if someone can point me in the correct direction to fix this. 
      Local $rDirectory = "H:\oDemandProject\fList.txt" Local $rLine = _FileCountLines($rDirectory) Local $x = 27 Local $y = 10 While $rline > 0 WinActivate("OnDemand", "-> 1") WinWaitActive("OnDemand", "-> 1") ControlClick("OnDemand", "", "[CLASS:AfxFrameOrView120u; INSTANCE:1]", "left", 4, $x, $y) $y += 15 $rLine -= 1 WEnd  
    • By Stacker
      Hi all,
      i have a file with coordinate ( ID,code,x,y,rotation,package,description)  like this :
      C2,CC001_100N,104445,69357,180,T-0603-08,100nF 10% 16V X7R 0603

      can i plot this file on screen with rectangle or picture related to package.
      Is possible on mouse over get information like "C2 CC001_100N T-0603-08 100nF 10% 16V X7R 0603" ?
      thanks for any tips
    • By nullschritt
      Hello, I originally started writing these functions in autoit, because of how easy it was to debug my code (the algorithms are actually implemented in php, though the same functionality could be used without conversion by using aucgi).
      My original intended purpose for these functions was to allow my web server to calculate if a player was between two points(inside a "region") in a game(minecraft).
      Currently my functions can do the following:
      Calculate the absolute distance between two points Calculate the volume between two points(to the nearest whole number) Calculate all points between two points, including their volume(to the nearest whole numbers) Check is a point is between two points(to the nearest whole number) ​(Maybe more I haven't though of?) I then expanded on the code to add some additional functionality. This code could be used with little modification to create a voxel style game engine. (It could actually even be further modified to support decimal values, though this would significantly slow it's performance exponentially per decimal place, though this shouldn't be necessary, except in rare cases such precision collision detection[ex: detect if a bullet hit a player or npc])
      I encourage everyone to submit your modifications/optimizations to my code so everyone can use them. I know my code isn't perfect, and it's functions could be expanded on with the right knowledge(things like collision detection, world generation, etc).
      If you use any of my code in your project, please link to this page! And while not required, I would like it if you please linked me to your project, I love to see my code in use!
      So finally here's the code(including examples of all functions being used):
  • Create New...