[Run] investigate DPI Awareness for font rendering

[enricogior]

On a 4K monitor at 200%

0.35:

PR #10568:

It's slightly better but far from ideal.

[enricogior]

In the app manifest, setting the dpiAwareness like this:

  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <dpiAwareness xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">PerMonitorV2</dpiAwareness>
    </windowsSettings>
  </application>

result:

but it's not placed in the center of the screen (shouldn't be too hard too fix the position).

[crutkas]

oooooooooooooooo

[crutkas]

this seems like an easy fix to add that, right?

[enricogior]

@crutkas

this seems like an easy fix to add that, right?

It depends, in FZ Editor we couldn't use it because of a framework bug that prevented us from fine controlling the windows position on non-primary monitors in some multi-monitor configuration where different DPI scaling factors are used.
For PT Run, given the less complex UI, the bug might not show up, but we need to test it.

[crutkas]

We should document that quirk but yes, i think this is a good item. put this in 39/41?

[enricogior]

@crutkas
we have a test app that shows the .Net DPI bug https://github.com/microsoft/PowerToys/tree/master/tools/FancyZonesEditor_DPI_test we need to add a readme to provide context.

[mykhailopylyp]

@enricogior @crutkas
A WPF application is not able to automatically handle dpi scaling without additional developer work. Take a look at High DPI Desktop Application Development on Windows. Positioning of PT Run is already dpi aware but height and width are not.

I'm wondering if it makes sense to postpone this item until we migrate to winui. Any thoughts?

[crutkas]

how easy is the fix?

[mykhailopylyp]

I think it is a medium-cost item. Also, probably we are going to have the same issues as in #5616. I don't think the same workaround will work for this issue.

[rinsuki]

Duplicate of #8949?

[Jay-o-Way]

Is this still an issue with the latest version? /needinfo

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.