Au3info doesn't compensate for DPI scaling

[anonymous]

I'm using Windows 10 on a laptop with a 1920x1080 screen with standard drivers. I sit a few feet away from the laptop, so I use DPI scaling to help me see the screen easier (Settings > System > Display > "Change the size of text, apps, and other items:"). Mine is currently set to 125%.

At this 125% DPI scaling setting (or anything greater than 100%), open the 'AutoIt v3 Window Info' program, turn on the option to magnify (Ctrl + Alt+ M), grab the finder tool, and point the target at some discernible object on your screen. Unless my system is somehow unique, or off the norm, you also will not see what you're pointing at in the small magnification window. If you move the target down and to the right some, you'll stumble onto what you were originally aiming for.

This is a DPI issue with AutoIt. Please fix it.

I believe this is also why PixelGetColor does not work properly under the same circumstances (a DPI scaling setting of over 100%).

Thank you for your attention.

[Melba23]

You can make your own scripts DPI-aware as explained here:
​https://www.autoitscript.com/forum/topic/182423-wrong-screen-resolution-displayed-by-autoit-macros/#comment-1310175

This is a "Feature Request" and will be moved.

M23

[TicketCleanup]

Automatic ticket cleanup.

[anonymous]

I promise you that this issue is not a feature request.... I've seen that post, and every other post on the AutoIt forums including the term DPI, and almost every post returned by Google ten pages deep into my searches on 'DPI scaling' and related searches that exist.

If the 'AutoIt v3 Window Info' program you distribute shows incorrect pixels in the magnify window while using the finder tool, as I've already clearly described (DPI scaling setting over 100%, point the finder tool target at something), that is a bug. If PixelGetColor returns incorrect values for any and all users who have a DPI scaling setting over 100%, that is a bug.

If you're not having these issues on your Windows system using a DPI scaling setting of over 100%, this still could be considered a bug. I don't seem to have this problem using Windows magnifier. The pixels directly under my cursor are what show up in its magnification area.

I could include DllCall("User32.dll","bool","SetProcessDPIAware") into every script I've ever written. It will not change what the magnify window shows when using the window info finder tool, nor will it return correct values using PixelGetColor using any of the PixelCoordMode settings.

Therefore, unless your solution to this problem is to require anyone using AutoIt to also not use DPI scaling, perhaps you should move this ticket back to Bug. Thanks.

[anonymous]

<snip>

[anonymous]

Adding DllCall("User32.dll","bool","SetProcessDPIAware") makes the scripts aware of the DPI scaling but the AutoIt v3 Window Info does not take DPI scaling into account. To find the correct mouse position, one would need to take the position values given by the Window Info and then multiply it manually by whatever you have your scaling set to. If you have it set to 150%, then you multiply by 1.5.

Is this something that will eventually be addressed with the Window Info? Perhaps having the Window Info detect what scaling is set to or allow users to manually enter in what scaling they are using so that the mouse positions will be accurate?

[Alekc]

Agree, this issue is very annoying.

[Jos]

It seems just a matter of changing the manifest of the program. I have made a trial version of the original au3info where I updated the manifest with reshacker and stored it here: ​https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/Au3Info.exe

Give it a try and let us know.

Jos

[anonymous]

Replying to Jos:

It seems just a matter of changing the manifest of the program. I have made a trial version of the original au3info where I updated the manifest with reshacker and stored it here: ​https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/Au3Info.exe

Give it a try and let us know.

Jos

Jos can you repost it. I get Not Found

The requested URL /autoit3/scite/download/beta_SciTE4AutoIt3/Au3Info.exe was not found on this server.

[Jos]

Replying to anonymous:

Jos can you repost it. I get Not Found

The requested URL /autoit3/scite/download/beta_SciTE4AutoIt3/Au3Info.exe was not found on this server.

It should be there again..

Jos

[Zdsl]

It displays the correct pixels now but now the window is very small on high resolution monitors since it doesn't use the system-wide DPI scaling now.

[Jos]

Understood but that would mean a change in the program in case that needs changing. I just demonstrated that the manifest needs updating for the dpi awareness.

I leave this ticket open to make the change permanent in the next versions.

Jos

[anonymous]

do you can to compile also x64 version of Au3Info.exe?

[Jos]

Replying to anonymous:

do you can to compile also x64 version of Au3Info.exe?

it's avaiable here now: ​https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/Au3Info_x64.exe

Jos

[anonymous]

Fixed? Its STILL a problem in teh latrest version.

[anonymous]

How is this set to fixed if the problem is still there and super annoying. I have 2 screens and 2 and 4k resolutions. 100% scaling is not an option for me. All other programs can understand scaling except this one. Ticked should be open, not set to fixed!