Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full and proper support for high DPI #20

Open
FenPhoenix opened this issue May 25, 2019 · 1 comment
Open

Full and proper support for high DPI #20

FenPhoenix opened this issue May 25, 2019 · 1 comment
Assignees

Comments

@FenPhoenix
Copy link
Owner

Right now, we just let Windows scale us as it sees fit, with the result that our UI looks slightly blurry when not at 100% scale, and I have reports that fonts may not be scaling quite as they should either. We might have to switch to .NET Framework 4.8 to do this, as judging from the release notes there's some high-DPI support improvements for WinForms in there that we might need. However, the requirements are the same as for 4.7.2, so it's not that much of a problem, other than making people download an entire new very large framework version that they may not have.

@FenPhoenix FenPhoenix added the enhancement New feature or request label May 25, 2019
@FenPhoenix FenPhoenix added this to the Version 1.1 milestone May 25, 2019
@FenPhoenix FenPhoenix self-assigned this May 25, 2019
@FenPhoenix FenPhoenix removed this from the Version 1.1 milestone Jun 13, 2019
@FenPhoenix
Copy link
Owner Author

FenPhoenix commented Jun 13, 2019

Reading about the goals for WinForms in .NET Core 3.0 ("Fix existing scaling bugs in Per Monitor DPI aware applications" and others), I'm going to wait for .NET Core 3.0's general release, then switch AL over. Till then, I'll hold tight with the imperfect scaling.

@FenPhoenix FenPhoenix added the postponed Will address, but waiting on something label Jun 13, 2019
@FenPhoenix FenPhoenix added this to the .NET Core 3.1 switch milestone Aug 18, 2019
@FenPhoenix FenPhoenix added wait for .NET Core 3.1 and removed postponed Will address, but waiting on something labels Aug 18, 2019
@FenPhoenix FenPhoenix modified the milestones: .NET Core 3.1 switch, fantasy super version Apr 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant