Messed up AutoIt GUI dimensions

[TheDcoder]

Hello, I just discovered a.... Bug? or Glitch... Here is it:

 

GUIs created with AutoIt are always larger than specified dimensions, i.e 16 pixels larger in width & 39 pixels in height, so If you want the exact dimensions, you need to subtract 16 from width & 39 from height... Here an example of a GUI with the same exact dimensions of command prompt:

#include <GUIConstantsEx.au3>

GUICreate("TEST", 677, 343)

GUISetState()

While 1
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            Exit

    EndSwitch
WEnd

Now open command prompt & see if they are the same in the size, this is the result for me:

But if you modify the code to this:

#include <GUIConstantsEx.au3>

Global Const $eGUI_WIDTH_CORRECTION = 16
Global Const $eGUI_HEIGHT_CORRECTION = 39

GUICreate("TEST", 677 - $eGUI_WIDTH_CORRECTION, 343 - $eGUI_HEIGHT_CORRECTION)

GUISetState()

While 1
    $nMsg = GUIGetMsg()
    Switch $nMsg
        Case $GUI_EVENT_CLOSE
            Exit

    EndSwitch
WEnd

They match perfectly... I would like to know if this is a bug or if there is some strange reason behind this :-/

 

Thanks in Advance, TD  

[Jon]

Windows sizes don't include all the chrome and title bars.

[guinness]

Those values are different system to system. Look at using _WinAPI_GetSystemMetrics() and one of the following indexes to obtain the correct value regardless of whether you're on 7/8/10 etc.

[TheDcoder]

@Jon Oh, Thanks!

@guinness Thanks!

[TheDcoder]

Hello,

Sorry for necro posting but I have a related issue and I think it's worth posting here instead of in another topic.

So my issue is, how do I get the left and top (X and Y) values of a window's "client area" which actually contains the content?

For example if a window has a title bar and a menu bar I want to offset the height of those to my relative coordinates from ControlGetPost.

[Melba23]

TheDcoder,

If I understand your question correctly, _WinAPI_ClientToScreen would seem to be the answer. Set the the client coordinates in the $tagPOINT structure to 0, 0 and the actual screen coordinates are returned.

M23

[TheDcoder]

Thanks @Melba23, that does look like what I want, will report back tomorrow after I test it

[TheDcoder]

On 2/25/2022 at 2:06 PM, Melba23 said:

_WinAPI_ClientToScreen would seem to be the answer. Set the the client coordinates in the $tagPOINT structure to 0, 0 and the actual screen coordinates are returned.

It works exactly like you described. My original goal was to get the coordinates relative to the window's client area itself, but that could be easily calculated with the help of this function. Thanks again

[Melba23]

TheDcoder,

Quote

My original goal was to get the coordinates relative to the window's client area itself

Then perhaps the _WinAPIScreenToClient function is what you need?

M23

[TheDcoder]

52 minutes ago, Melba23 said:

Then perhaps the _WinAPIScreenToClient function is what you need?

That won't work as I have the control's coordinates, not the absolute screen coordinates. I am using ControlGetPos function and it returns coordinates relative to the window, but it is relative to the client area.

Thus my question about converting client area coordinates to actual window coordinates or screen coordinates (which can be converted into window coordinates too).