PureBasic Forum

It seems as if the DesktopXYZ() commands output wrong coordinates when the compileroption DPI awareness is enabled.

Based on chis code this can be reproduced with the following sniplet.

Regardless of the compiler option "DPI aware" the real physical desktop size, mouse position etc. should be returned. At least that's what I would expect from the help texts for the commands. But this isn't the case.

My Desktopwidth is 1920 pixel, but the DPI aware compiled code shows a width of 1536 pixels (I use a desktopscaling of 125 %).

PB Help wrote:
"DesktopWidth(#Desktop) - Returns the width of the specified desktop. "

Greetings
Kurzer

- deleted -

I didn't even know DesktopMouseX() was a thing. I was always using "mouse.POINT" and "mouse\x" in my code. When this bug gets fixed I'll switch to DesktopMouseX() in future.

Sorry, my previous post was incomplete and misleading.

I can confirm the problem with DesktopWidth() and DesktopHeight(), using PB 5.71 beta 1 (x64) on Windows 10 version 1809 with DPI 125 %.

DesktopMouseX() and DesktopMouseY() yield the same values though, regardless whether the program is compiled with or without the "DPI aware" flag.

Interesting. I use Windows 7 x64 (PB 5.70 LTS) and all 4 values are wrong in DPI aware mode:

Interesting indeed.

The problem is, that different Windows versions handle DPI awareness in different ways.
After Windows 7, there were significant changes especially in Windows 8.1.
Windows 10 introduced more changes, and even different versions of Windows 10 behave differently in this regard.
For more details see e.g. https://kynosarges.org/WindowsDpi.html

Fred has to handle all that for PureBasic. I don't envy him for that.

Fixed.

Thank you, Fred!

Are you soon going to release a beta 2 version?
I really would appreciate that!

Fix confirmed with PB 5.71 beta 2 (x64).