DPI Awareness , any suggestion ?

[Jowy]

Hello dears,

I'm trying to write a script in AutoIT but, I have issue in DPI. I'm basically a Lead Software Developer and I use AutoIT from time to time. I have an ERP Launcher that should work on all machines starting by Windows 7, Windows 8.x , Windows 10, Windows Server 2003/2008/2012.

When I was searching in AutoIT forum, I could see previously this " Writing DPI Awareness App - workaround" in the signature of Mr. @mLipok,, but clicking on the link, => page not found.

Do you have any new link or something that you can share with me ? I'm using macbook pro with retina display and VMware machines: Windows 10 and Server 2012 as development machines, but both of them they have 200% scaling and they have AutoIT installed. In this case, when I use Koda (blurry font for sure), I have the controls as I want, and application is working fine, but also blurry font, until it is used on 96 DPI machine.

Now, in windows 10, with DPI System Enhanced feature in the compatibility tab, the application running on 200% scaling is excellent visual like it's running on 96 DPI without touching my code and without doing anything, but no all clients they have windows 10. It seems Microsoft worked a lot on the new feature. But for other machines like windows 7/8/2012, the font is blurry if the clients have scaling above 100% (more than 96 DPI). I know how to enable hidpi stuff in the wrapper and I know how to write the code to use a scaling factor that can be multiplied by every coordinate, but this way is cumbersome and I have to change all coordinates of all X, Y, Width, Height after getting the code from Koda. Is there a fast way ? 

So, what do you recommend me guys ?

Thanks,

Jowy

[Subz]

Try:

 

[Jowy]

  On 2/18/2018 at 8:36 AM, Subz said:

Try:

 

Expand  

I have tried it, but same still blurry on 2012 and windows 10, any other suggestion ?

[Subz]

Does the following registry key equal 192 (200% DPI)?

RegRead ("HKEY_CURRENT_CONFIG\Software\Fonts", "LogPixels")

[Jowy]

  On 2/18/2018 at 12:10 PM, Subz said:

Does the following registry key equal 192 (200% DPI)?

RegRead ("HKEY_CURRENT_CONFIG\Software\Fonts", "LogPixels")

Expand  

On windows 10 (my development machine) it's 96 and the scaling is 200% kindly find attached screenshot:

[Subz]

Actually might be barking up the wrong tree here, the key refers to the font scaling, i.e. under Advanced display settings » Advanced sizing of text and other items » Set a custom scaling level, which allows you to change the font scaling to match screen dpi, but I'm guessing you're not after this.

 

[Jowy]

  On 2/18/2018 at 12:31 PM, Subz said:

Actually might be barking up the wrong tree here, the key refers to the font scaling, i.e. under Advanced display settings » Advanced sizing of text and other items » Set a custom scaling level, which allows you to change the font scaling to match screen dpi, but I'm guessing you're not after this.

 

Expand  

As far as I know , the AppliedDPI is the one showing the scaling... 

[Jowy]

  On 2/18/2018 at 1:11 PM, Jowy said:

As far as I know , the AppliedDPI is the one showing the scaling... 

Expand  

Now, applying the example with the following and building the Example, check please the following screenshot: the 2 windows is small, one I replied yes for DPI awareness and the other I answered no. I run the exe file from explorer. But if I run through the editor with F5 (with GO option), and since the editor is not DPI aware, for sure you will have same results whether you say yes or no for DPI.

 

Edited February 19, 2018 by Jowy

[RTFC]

Maybe this thread helps:

https://www.autoitscript.com/forum/topic/182423-wrong-screen-resolution-displayed-by-autoit-macros/

 

[Jowy]

  On 2/18/2018 at 1:23 PM, RTFC said:

Maybe this thread helps:

https://www.autoitscript.com/forum/topic/182423-wrong-screen-resolution-displayed-by-autoit-macros/

 

Expand  

Hello @RTFC, I have tried the code inside, but it's giving me null for width and height... Anyway, it seems I'll go back for the workaround of scale factor multiplied by each x,y,w,h... , in the workaround, I can at least stretch even the window width on hi-dpi screens.

Edited February 19, 2018 by Jowy

[BrewManNH]

STOP posting screenshots of your code, post the code. By posting screenshots, you're making it so that everyone testing this has to retype your code instead of copy-paste. You're going to get a lot less people willing to help you.

[Melba23]

Jowy,

As BrewManNH has asked above, please use Code tags to post your code - see here how to do it.

M23

 

[Jowy]

  On 2/19/2018 at 2:10 PM, Melba23 said:

Jowy,

As BrewManNH has asked above, please use Code tags to post your code - see here how to do it.

M23

 

Expand  

Thanks Melba, it wasn't interesting code actually, it was the examples and codes from other links proposed from guys in the forum and from the Examples code that comes with AutoIT. Next time, I'll put the code.

[Jowy]

  On 2/19/2018 at 2:06 PM, BrewManNH said:

STOP posting screenshots of your code, post the code. By posting screenshots, you're making it so that everyone testing this has to retype your code instead of copy-paste. You're going to get a lot less people willing to help you.

Expand  

Sure Next time will put the code,  it wasn't interesting code actually, it was the examples and codes from other links proposed from guys in the forum and from the Examples code that comes with AutoIT. Next time, I'll put the code. I was only showing the DPI resolution difference.

[tonycst]

LOL on posting code screenshots

So sad, to this day i cant find a working simple solution to DPI problem.

Just because i know the scaling factor, does not make built in Pixelsearhch function to work.

I think its a bug. If pixelsearch reports incorrect coordinates, its a bug

[qwert]

@tonycst:  Fully supporting DPI settings is one of the toughest, most convoluted problems I've come upon with Au3 GUIs.  Blurry graphics and enlarged text are just the basic aspects to solve—and are the ones some of the forum posts have "solved".  But then you move to cursor coordinates.  And when you think you have things in hand, try your GUI on a tablet PC that swaps everything to a vertical orientation when you rotate the tablet.  The real topper is a dual monitor system where the monitors are running at different resolutions.

Last week, I happened upon the following observations and conclusions:

  Quote

"DPI unaware applications render as if the screen that they are on has a DPI value of 96. Whenever these applications are run on a screen with a display scale greater than 100% (> 96 DPI), Windows will stretch the application blurry."

http://www.kynosarges.org/WindowsDpi.html
HOWEVER, Windows 10 “Creators Update” largely eliminated the various application issues discussed in this (above) article.  Read this, instead:

http://news.kynosarges.org/2017/04/16/dpi-settings-in-windows-10-creators-update/
"Windows 10 started its journey to simplified display settings with an awkward combination of dialogs in the modern Settings app and the legacy Control Panel, as described in my previous post on the subject. With the recently released “Creators Update??? (version 1703) the journey appears to have reached its destination. All display settings, including all DPI settings, are now exclusively handled by the Settings app and have been further streamlined as well."

 

Expand  

Now, I'll quickly admit that I have yet to make corresponding adjustments to my GUI scripts.  But, I'll proceed with these new roadmaps in hand.  It's encouraging that there's been some progress from the operating system side.  As a first step, I'm back experimenting the the DPI Aware setting for GUIs on Win10.  But then I have Win7 and Win8 environments to consider.

Hope this helps.

 

[mLipok]

btw.
added to the WIKI

https://www.autoitscript.com/wiki/FAQ#DPI_Awareness