Real Window Width/Height, WindowBlinds

[MarkRobbins]

I'm using WindowBlinds, VOX 2 Style. When I WinMove() the width and height show quite a bit short when measured on screen (14px!), WinGetPos() returns the proper numbers, but when attempting placement of windows this is quite a pain. Is there a solution for this other than constant compensation?

 

[Edano]

this is quite strange. there is a difference between window and client area, but wingetpos() should always correspond to winmove(). if you have a constant distortion, i would use that as a global variable at the beginning and compensate it.

you could also try

_WinAPI_GetSystemMetrics()

http://winapi.freetechsecrets.com/win32/WIN32GetSystemMetrics.htm

Edited July 30, 2013 by Edano

[Melba23]

MarkRobbins,

When you create a GUI, the client area is set to the dimensions you use in GUICreate. But other Win* commands use the entire GUI size (including borders).

The trick is to create the GUI and then immediately use WinGetPos to find out the overall size - these values can then be used in subsequent commands which use the the size parameters.

M23

[Edano]

MarkRobbins,

When you create a GUI, the client area is set to the dimensions you use in GUICreate. But other Win* commands use the entire GUI size (including borders).

The trick is to create the GUI and then immediately use WinGetPos to find out the overall size - these values can then be used in subsequent commands which use the the size parameters.

M23

.

yes, but he says that winmove() does not work correctly when he checks it with wingetpos(). that is really weird.

 

Edit: as far as i understood it.

Edited July 30, 2013 by Edano

[MarkRobbins]

All:

WinMove and WinGetPos are in synch, the problem is that the window measured on the screen ends up being smaller than WinMove, and smaller than WinGetPos. I am not talking about GUICreated windows, which take the client dimensions.

[Edano]

All:

WinMove and WinGetPos are in synch, the problem is that the window measured on the screen ends up being smaller than WinMove, and smaller than WinGetPos. I am not talking about GUICreated windows, which take the client dimensions.

.

and how do you measure it ?

maybe your desktop style adds an invisual border of 7 px right and left ?

[MarkRobbins]

.

and how do you measure it ?

maybe your desktop style adds an invisual border of 7 px right and left ?

 

The Left and Top are correct, the width and height are short 14px onscreen. Maybe if I turn shadows off?

[BrewManNH]

What makes you think that the window is 14 pixels smaller than what WinGetPos tells you it is? If you're using WinMove, and then reading the w/h with WinGetPos, and WinGetPos tells you that the Window is the size you set in the WinMove command, I'm not seeing where you're coming up with a 14 pixel difference.

[MarkRobbins]

What makes you think that the window is 14 pixels smaller than what WinGetPos tells you it is? If you're using WinMove, and then reading the w/h with WinGetPos, and WinGetPos tells you that the Window is the size you set in the WinMove command, I'm not seeing where you're coming up with a 14 pixel difference.

 

In the image the grey rectangle is put in, upon the screen capture. The grey rect is 14 px short of what WinGetPos reports. I've also used a pixel ruler onscreen... and, the whole issue came to my attention when I tried to put two windows side by side using data autoit is reporting for the windows.... there was a visual gap

[BrewManNH]

You're not making things any clearer.

Where does the grey rectangle come from, and what tells you that it's 14 pixels smaller than it should be? Maybe your grey rectangle is at fault and not anything else you're reading. Are you sure it's not something to do with your WindowsBlinds altering the size of things? Also, the Left and Top are where the top left corner is located, it's always going to be where you tell it to be, they're immaterial to the question at hand.

BTW, can you make a better screen shot? That one is nearly impossible to make out what is what.