DPI per Monitor

[onesounds]

What's the PR

• ref https://learn.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dpi-awareness-for-a-process
• from Made PT Launcher per-monitor DPI aware microsoft/PowerToys#32882
• Fixes blurry window when DPI is changed in dual monitor state.
• Previously, in two DPI states, the behavior was based on the DPI of one side, causing problems with sharpness on the other side. After this change, it will render to the DPI of each monitor.

Test Case

• 10 You must have at least two monitors.
• 20 In an flow(dev), change the dpi to see what happens when you get a blurry state (175, 200, 225, 250...)
• 30 build this PR
• 40 goto 20

[VictoriousRaptor]

@taooceros Should we set use winforms to false? Code of pt run.

[taooceros]

@taooceros Should we set use winforms to false? Code of pt run.

I think that would cause some compilation failure. Seems like we still use some part of winform? Though I think it is resolvable.

[onesounds]

@taooceros Should we set use winforms to false? Code of pt run.

I think that would cause some compilation failure. Seems like we still use some part of winform? Though I think it is resolvable.

@VictoriousRaptor @taooceros I tried (false UseWindowsForms) and The build was successful. but I've been searching too, and as taoo said, they said it does affect winform-dependent code. (but why build success?)

We can either change it to false and see what happens, or we can safely leave it at true. What do we choose?
(I confirmed that this PR is works well by working on another PR.)

[taooceros]

@taooceros Should we set use winforms to false? Code of pt run.

I think that would cause some compilation failure. Seems like we still use some part of winform? Though I think it is resolvable.

@VictoriousRaptor @taooceros I tried (false UseWindowsForms) and The build was successful. but I've been searching too, and as taoo said, they said it does affect winform-dependent code. (but why build success?)

We can either change it to false and see what happens, or we can safely leave it at true. What do we choose? (I confirmed that this PR is works well by working on another PR.)

If it builds, I think it will work. Let's do it and rollback if anything observed. I don't think we really use much winform related functionality.

[onesounds]

@taooceros Should we set use winforms to false? Code of pt run.

I think that would cause some compilation failure. Seems like we still use some part of winform? Though I think it is resolvable.

@VictoriousRaptor @taooceros I tried (false UseWindowsForms) and The build was successful. but I've been searching too, and as taoo said, they said it does affect winform-dependent code. (but why build success?)
We can either change it to false and see what happens, or we can safely leave it at true. What do we choose? (I confirmed that this PR is works well by working on another PR.)

If it builds, I think it will work. Let's do it and rollback if anything observed. I don't think we really use much winform related functionality.

OK. puhsed.