![]() This way no key press is needed, so we can test screen savers, too. ReturnIt shows a tooltip with the screen and window size information. It works in my laptop, but please tell me your experiments with external monitors. Because of the rounding errors I changed the tests in the script, allowing an error of 2 pixels. This is why we need to establish the screen resolution beforehand. Windows calculates the actual width and height of the current window in the original (native) resolution, which could have rounding errors. There is a problem, if the screen resolution changes. Value := -1*TwosComplement( value, size ) ReadInteger( p_type, p_address, p_offset, p_hex=true ) "`n`nIsZoomed = " DllCall( "IsZoomed", "uint", hw_active ) Y2 := ReadInteger( "int4", &rect, 12, false ) X2 := ReadInteger( "int4", &rect, 8, false ) Y1 := ReadInteger( "int4", &rect, 4, false ) X1 := ReadInteger( "int4", &rect, 0, false ) Status := DllCall( "GetWindowRect", "uint", hw_active, "uint", &rect ) "A_ScreenWidth = " A_ScreenWidth ", A_ScreenHeight = " A_ScreenHeight In any case, the returned size is unreliable when the window is maximized. I think it demonstrates that the window size returned is a Windows "bug" (or feature?). This is different from maximizing a window. Notice that a full screen game, such as pinball, operates in a different video mode. What's going on with window sizes bigger than the screen? ![]() and with the taskbar visible, the only difference is height = 748. Just testing on any program with a maximized window (not a full-screen game), with the taskbar set to auto-hide, I get:Ī_ScreenWidth = 1024, A_ScreenHeight = 768
0 Comments
Leave a Reply. |