[PATCH 0/1] MR7456: Draft: [RFC] ddraw/tests: Set DPI awareness to avoid unexpected clip rect.

[Bernhard Übelacker (＠bernhardu)]

Hello, I wondered about the ddraw* tests, which show a similar message `Expect clip rect (0,0)-(1920,1080), got (0,0)-(1536,864).` over a range of Windows 10 machines.

This seems the same as discussed in: https://bugs.winehq.org//show_bug.cgi?id=54068 .

I searched just the internet for "1536,864" which also points to the direction of something DPI related.

So I tested if it disappears with a call to `SetProcessDpiAwareness(PROCESS_PER_MONITOR_DPI_AWARE);`, and in seems it does. https://testbot.winehq.org/JobDetails.pl?Key=151556

(The failures with debiant and w11pro64_amd seem to be also there with a null patch: https://testbot.winehq.org/JobDetails.pl?Key=151557 )

Would such a change be acceptable, or would it defeat the purpose of the test?