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

Support HighDPI in Windows #263

Closed
arnowelzel opened this issue Dec 24, 2023 · 2 comments
Closed

Support HighDPI in Windows #263

arnowelzel opened this issue Dec 24, 2023 · 2 comments

Comments

@arnowelzel
Copy link

Is your feature request related to a problem? Please describe.
It seems, the Windows version is not DPI aware and when using it with scaling on a 4K display, the UI does not look very nice.

Describe the solution you'd like
It would be nice if the application had DPI awareness enabled and if needed using icons and bitmap rendering with upscaling to keep the original size.

Describe alternatives you've considered
I tried to enable advanced system upscaling in the application properties in Windows, but this did not help.

Additional context
See the screenshot here - this demonstrates the issue. The title bar is in rendered at the native resolution while the application content is blurred as it is only upscaled due to the missing DPI awareness:

image

Another example - the profile edit dialog:

image

@arnowelzel
Copy link
Author

I started adding an app.manifest file to the application with the respective settings and use the need initialization. So getting DPI awareness is quite simple. However there is still work to do to handle the stored Window size as DPI independent value and to handle toolbar icons and bitmaps as device independent images which upscale if needed. Also the dialog element sizes may need to be adjusted depending on the display scaling:

image

However text and native Windows Forms controls in dialog windows already look much nicer this way:

image

@cyanfish
Copy link
Owner

#182 is a previous issue for this. My current plan is to do this after #81 which I think will make addressing element sizes easier.

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

2 participants