Seeking guidance on DPI Awareness

[qwert]

With all the new hi-pixel monitors (e.g., 1920 pixels on a laptop), more problems are showing up when users set their operating system's display scaling to 125% or 150%.

I've been investigating solutions, here and on the msdn pages. This page has a good overview: https://msdn.microsoft.com/en-us/library/windows/desktop/dn280512(v=vs.85).aspx

Among the details is this statement: "Because of DPI virtualization, if one application queries another with a different awareness level for DPI-dependent information, the system will automatically scale values to match the awareness level of the caller."

Does this mean that if an Au3 script declares itself as DPI aware and then calls another script—or runs an external application—that the called script or application will then be DPI aware? (I realize this is two different questions.)

If not, is there a way that an Au3 script can force (i.e., change) an external application to be DPI aware.

Advice from anyone with DPI experience will be greatly appreciated.  Thanks in advance.

 

 

 

 

 

Edited December 20, 2016 by qwert

[mLipok]

 

 

[qwert]

Indeed, those are the example scripts that I've been testing with.

But what I'm seeking is a higher "strategy"—if it's possible—to have DPI awareness imposed from one script onto another ... and even from an Au3 script onto an external application. Those issues are the basis of my post. And other than the one sentence on msdn, I've haven't found any references.

Thanks for your response.

[mLipok]

Did you try:

#AutoIt3Wrapper_Res_HiDpi=                      ;(Y/N) Compile for high DPI. Default=N

?

[BrewManNH]

You can't make another non-dpi aware program magically become DPI aware by interacting with it.

What the article stated is that it would act as if the other program were DPI aware in determining what the size of the window might be when you try to get it's size, so you'll get an incorrect size returned when using GetWindowRect (or WinGetPOS for example).