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

[HiDPI] Incorrect UI Scaling on 4K Display #1587

Open
WeaponizedMeme opened this Issue Sep 7, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@WeaponizedMeme

WeaponizedMeme commented Sep 7, 2018

Images

The window relative to notepad
You can see here the option windows scale fine, it's just the main window

Expected behavior

The UI to scale properly . During the setup it looked great, and when i open any of the options menus it looks normal(as shown in the image above). But the main window is fucked.

Actual behavior

Main window is microscopic.

Does it work in stable version?

No

Steps to reproduce that behavior

Use a 4K monitor and set DpiAware=1 in Mirandaboot.ini

Really hoping this is fixed, because Pidgin is no longer being updated and I've been trying to find a client that has DPI support.

@dartraiden

This comment has been minimized.

Show comment
Hide comment
@dartraiden

dartraiden Sep 7, 2018

Member

None of the developers have 4K screens. Perhaps things will go better when we move on to Qt.

Member

dartraiden commented Sep 7, 2018

None of the developers have 4K screens. Perhaps things will go better when we move on to Qt.

@dartraiden dartraiden changed the title from Incorrect UI Scaling on 4K Display to [HiDPI] Incorrect UI Scaling on 4K Display Sep 7, 2018

@WeaponizedMeme

This comment has been minimized.

Show comment
Hide comment
@WeaponizedMeme

WeaponizedMeme Sep 9, 2018

@dartraiden Understood. Can't wait for the QT move, then I will finally have a 4K-compatible jabber client!

WeaponizedMeme commented Sep 9, 2018

@dartraiden Understood. Can't wait for the QT move, then I will finally have a 4K-compatible jabber client!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment