Autoit and DPI awareness

[Spiff59]

I'm finding users adjusting the default screen DPI setting far more often in Windows 7 than I ever experienced with Windows XP.

Perhaps the setting is now more prominently displayed or easily found than when is was in the advanced section of the settings tab of the display options window.

Most commercial applications seem to adapt to the DPI value without a glitch, but Autoit only partially conforms to this system-wide setting.

The fonts within controls are affected, yet the overall control dimensions are not.  The result are labels, buttons, etc, with txt that is truncated or unreadable. Some special controls or API functions in Autoit, like calendar, are also affected by the DPI setting.  

I've overridden non-default DPI settings by calling this at the top of programs:

Func GetDPI_Ratio()
    Local $hWnd = 0
    Local $hDC = DllCall("user32.dll", "long", "GetDC", "long", $hWnd)
    Local $aRet = DllCall("gdi32.dll", "long", "GetDeviceCaps", "long", $hDC[0], "long", 90)
    $hDC = DllCall("user32.dll", "long", "ReleaseDC", "long", $hWnd, "long", $hDC)
    If $aRet[0] = 0 Then $aRet[0] = 96
    Return $aRet[0] / 96
EndFunc

It returns an $iDPI_Ratio global such as 1 or 1.25. I then replace all calls to GUISetFont() and GUICtrlSetFont() with calls to user functions like GUISetFont_DPI() and GUICtrlSetFont_DPI() which apply the $iDPI_Ratio variable as a divisor to the font size parameter like this:

Func GUISetFont_DPI($isize, $iweight = "", $iattribute = "", $sfontname = "")
    GUISetFont($isize / $iDPI_Ratio, $iweight, $iattribute, $sfontname)
EndFunc

I'm still left with a few uncorrected issues like calendar controls.  I considered a bugtracker to request an extra parm for GUISetFont() and GUICtrlSetFont(), that would act as a DPI divisor and default to 1.  That would greatly simplify programatically suppressing a non-standard DPI setting. Then I wonder if perhaps the goal should be to move in the opposite direction... that of making Autoit fully DPI-aware?

It appears the available values for the DPI setting are:

.75

1.00 (default)

1.25

1.50

2.00

[Jon]

I've started using Windows on a high-dpi screen and I know what you mean. It's easy to tag the exes with the DPIAwareness manifest but there's a lot of testing/work to make it look right. The only file I've tagged so far is Aut2Exe (Beta) which looks OK - but normal GUIs fell to pieces so its one for the furture.

[jchd]

Is that a sign of hesitation between future and torture?