cyx54tc

convert control coordinate to screen coordinate

4 posts in this topic

Hi I wonder how i can convert a control coordinate to screen coordinate and the other way around? For example i tried it on note pad with the AutoIt window info tool

>>>> Window <<<<
Title: Untitled - Notepad
Class: Notepad
Position: -8, -8
Size: 1936, 1056
Style: 0x15CF0000
ExStyle: 0x00000110
Handle: 0x00000000002C04BE

>>>> Control <<<<
Class: Edit
Instance: 1
ClassnameNN: Edit1
Name: 
Advanced (Class): [CLASS:Edit; INSTANCE:1]
ID: 15
Text: 
Position: 0, 0
Size: 1920, 998
ControlClick Coords: 0, 0
Style: 0(removed)
ExStyle: (removed)
Handle: (removed)

>>>> Mouse <<<<
Position: 0, 42
Cursor ID: 0
Color: 0x292826

>>>> StatusBar <<<<
1: 
2:    Ln 1, Col 1 

>>>> ToolsBar <<<<

>>>> Visible Text <<<<

>>>> Hidden Text <<<<

you can see that my mouse is at screen (0, 42) and (0, 0) for the control. But the position of the control is also (0,0) (why??). Then the window position is (-8,-8) (why?? its full screen mode so i expect it to be (0,0))

any help is appreciated. Thanks

Share this post


Link to post
Share on other sites



you can see that my mouse is at screen (0, 42) and (0, 0) for the control. But the position of the control is also (0,0) (why??). Then the window position is (-8,-8) (why?? its full screen mode so i expect it to be (0,0))

 

Interesting... same observation . I did not notice this before.

mLipok


Signature beginning:   Wondering who uses AutoIT and what it can be used for ?
* GHAPI UDF - modest begining - comunication with GitHub REST API *
ADO.au3 UDF     POP3.au3 UDF     XML.au3 UDF    How to use IE.au3  UDF with  AutoIt v3.3.14.x  for other useful stuff click the following button

Spoiler

Any of my own code posted anywhere on the forum is available for use by others without any restriction of any kind. 

My contribution (my own projects): * Debenu Quick PDF Library - UDF * Debenu PDF Viewer SDK - UDF * Acrobat Reader - ActiveX Viewer * UDF for PDFCreator v1.x.x * XZip - UDF * AppCompatFlags UDF * CrowdinAPI UDF * _WinMergeCompare2Files() * _JavaExceptionAdd() * _IsBeta() * Writing DPI Awareness App - workaround * _AutoIt_RequiredVersion() * Chilkatsoft.au3 UDF * TeamViewer.au3 UDF * JavaManagement UDF * VIES over SOAP * WinSCP UDF * GHAPI UDF - modest begining - comunication with GitHub REST API *

My contribution to others projects or UDF based on  others projects: * _sql.au3 UDF  * POP3.au3 UDF *  RTF Printer - UDF * XML.au3 - BETA * ADO.au3 UDF SMTP Mailer UDF *

Useful links: * Forum Rules * Forum etiquette *  Forum Information and FAQs * How to post code on the forum * AutoIt Online Documentation * AutoIt Online Beta Documentation * SciTE4AutoIt3 getting started * Convert text blocks to AutoIt code * Games made in Autoit * Programming related sites * Polish AutoIt Tutorial * DllCall Code Generator * 

Wiki: Expand your knowledge - AutoIt Wiki * Collection of User Defined Functions * How to use HelpFile * Best coding practices * 

IE Related:  * How to use IE.au3  UDF with  AutoIt v3.3.14.x * Why isn't Autoit able to click a Javascript Dialog? * Clicking javascript button with no ID * IE document >> save as MHT file * IETab Switcher (by LarsJ ) * HTML Entities * _IEquerySelectorAll() (by uncommon) * 

I encourage you to read: * Global Vars * Best Coding Practices * Please explain code used in Help file for several File functions * OOP-like approach in AutoIt * UDF-Spec Questions *  EXAMPLE: How To Catch ConsoleWrite() output to a file or to CMD *

"Homo sum; humani nil a me alienum puto" - Publius Terentius Afer
"Program are meant to be read by humans and only incidentally for computers and execute" - Donald Knuth, "The Art of Computer Programming"
:naughty:  :ranting:, be  :) and       \\//_.

Anticipating Errors :  "Any program that accepts data from a user must include code to validate that data before sending it to the data store. You cannot rely on the data store, ...., or even your programming language to notify you of problems. You must check every byte entered by your users, making sure that data is the correct type for its field and that required fields are not empty."

Signature last update: 2017-06-04

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

The -8.-8 is because the window still has its border in fullscreen mode. It's just displayed outside of the viewport (by 8 pixels). If you have a dual monitor setup you can easily see it:

1) maximize your SciTE window (for instance) on the right monitor by placing it there and double-clicking the title bar. It will then have a position of -8,-8 (in case of default window manager) if your left monitor is the default display, or -8 + <monitor display width> if your right monitor is the main display.

2) Now drag the title bar of the maximized window, you should see the border on the far right of the left monitor shortly appearing and disappearing, because Windows hides that superfluous border but apparently it's a bit glitchy in that short moment.

/edit: also note that the width of the entire window is 1936, i.e. 1920 + 2*8.

And 0,42 is the first pixel of the edit control in maximized notepad, which is 0,0 relative to the control itself, so absolute mouse pointer position 0,42 corresponds to a control click of the control in question (the big edit part of the notepad window) at 0,0.

Now if you play with the Coord Mode setting in the options menu of the info tool, you'll see your mouse x,y coordinates change. "Screen": absolute screen position. Upper left mouse position is 0,0. "Window":  to relative to the top left window corner  (which means the off-screen border at -8,-8), in this mode your mouse will not go below 8,8. "Client": relative to the client area of the window, meaning your mouse will be 42 pixels above the edit control of the notepad window at 0,-42.

(These coordinate modes can be set in your script too, influencing the results you get from coordinate getter methods. Check the help for the opt() method and search for "coordmode".)

Edited by SadBunny

Roses are FF0000, violets are 0000FF... All my base are belong to you.

Share this post


Link to post
Share on other sites

The -8.-8 is because the window still has its border in fullscreen mode. It's just displayed outside of the viewport (by 8 pixels). If you have a dual monitor setup you can easily see it:

1) maximize your SciTE window (for instance) on the right monitor by placing it there and double-clicking the title bar. It will then have a position of -8,-8 (in case of default window manager) if your left monitor is the default display, or -8 + <monitor display width> if your right monitor is the main display.

2) Now drag the title bar of the maximized window, you should see the border on the far right of the left monitor shortly appearing and disappearing, because Windows hides that superfluous border but apparently it's a bit glitchy in that short moment.

/edit: also note that the width of the entire window is 1936, i.e. 1920 + 2*8.

And 0,42 is the first pixel of the edit control in maximized notepad, which is 0,0 relative to the control itself, so absolute mouse pointer position 0,42 corresponds to a control click of the control in question (the big edit part of the notepad window) at 0,0.

um, this explains alot. But why is the position of the editor control (0,0) though? and how can i get the screen coordinate from the control coordinate and vice versa?

Share this post


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