Problems with 4k (3840×2160) resolution.

[KrabKley]

I took a screenshot with a desktop resolution of 3840×2160 and when using the program Au3Info_x64.exe I was trying to determine the pixel. But I was never able to get a hold of him. The cursor was jumping and then I realized that Au3Info_x64.exe incorrectly determines the resolution of the monitor. Au3Info_x64.exe he says that I have 2k and this is not true. I have a resolution of 3840×2160 and the program defines 2560х1440.

How to fix it?

 

 

Edited May 30, 2023 by KrabKley

[KaFu]

I guess you have set you DPI to 150%?

[KrabKley]

thank you very much. It seems to be the only way. Windows itself defaults to a scale of 150%. at 100% nothing is visible even on a 32 monitor)

[Shark007]

The cure is to recognize the scaling within your App.

#AutoIt3Wrapper_Res_HiDpi=Y

#include <GDIPlus.au3>

_GDIPlus_Startup()
Global $iScale = DllCall($__g_hGDIPDll, "int", "GdipGetDpiX", "handle", _GDIPlus_GraphicsCreateFromHWND(0), "float*", 0)[2] / 96 ;read Windows scaling
_GDIPlus_Shutdown()
If Not $iScale >= 1 Then $iScale = 1

;Now you need to add [* $iScale] to all the dimensions as such . . .

GUICtrlCreateButton("button", 295 * $iScale, 35 * $iScale, 20 * $iScale, 24 * $iScale)

 

Edited May 30, 2023 by Shark007

[paw]

Quote

Change Au3Info application properties In Explorer or on the Start menu, right-click the application name, select Properties, select the Compatibility tab, and then set Override high DPI scaling behavior, scaling performed by: Application.

 

[KrabKley]

On 6/3/2023 at 7:35 PM, paw said:

This is the best and easiest solution. Before launching, changing the DPI to 100 and then back to 150 is also a solution, but much worse). Thanks