Broken UI on high DPI screen in v2.3.50.0
Tennyleaz opened this issue · comments
Thanks for reporting! Ironically, I've made the latest changes solely to support High DPI screens.
On my daily development machine I do have a High DPI screen myself, setting to 150% scale.
While I do not get the erroneous display as in your screenshot, I might suspect that the DevExpress UI components I'm using are doing some DirectX stuff in the background, thus generating the errors you see.
I'll try to see whether I can disable DirectX support altogether.
Another issue might be the non-western characters like Chinese or Korean that I did not test with.
A very fast reply!
Might not related, but this is my current environment:
- Windows 10 22H2, x64
- Dual screens, primary is 1440p 150%, secondary is 1080p 100%
- Ryzen 7 5700G with Radeon Graphics, driver version 23.5.2
I've done a very quick fix, by simply not calling this line of code anymore:
WindowsFormsSettings.ForceDirectXPaint();
I've just published a new setup with this change.
Could you please take a look and give it a try whether things improve/change/worsen by this?
This is how it looks on my 150% display:
![image](https://private-user-images.githubusercontent.com/415439/253492543-257b55b7-cf13-4127-91e2-55798acb4fe7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDM5MzM2MTEsIm5iZiI6MTcwMzkzMzMxMSwicGF0aCI6Ii80MTU0MzkvMjUzNDkyNTQzLTI1N2I1NWI3LWNmMTMtNDEyNy05MWUyLTU1Nzk4YWNiNGZlNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjMxMjMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDIzMTIzMFQxMDQ4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04NTcxYTQ2MzJjODYyNDI2ZTczYTJhOTBlYmI1ZTkxNjk1ZDIzNTk5M2Y2ODY0YjU5MzU2ODc3ZDFjM2Q5ZjdhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.uNkMIK2m_napDsgqshz4qFlrwjUTU9dsxuhDLS_-Dr0)
It seems to be somewhat sharper than in your screenshot.
Honestly, I have no idea why this behaves so differently.
The application uses "Segoe UI" font.
On my Windows 11 system, I have these one installed:
![image](https://private-user-images.githubusercontent.com/415439/253493482-ee239749-e882-447c-8663-cf39f3b35aa6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDM5MzM2MTEsIm5iZiI6MTcwMzkzMzMxMSwicGF0aCI6Ii80MTU0MzkvMjUzNDkzNDgyLWVlMjM5NzQ5LWU4ODItNDQ3Yy04NjYzLWNmMzlmM2IzNWFhNi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjMxMjMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDIzMTIzMFQxMDQ4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iYjUxYTA5MGZhYjhiZDM3YWNiZTA0ZjQwMjhkMzEwYzMzMDA4MGZmNDhlYWZiNGUwMTIyOWEyOWJlNTBiMDlhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.JA1nIJxGM38kMj9XnlkAW8g1tlv77ekeNtXXx6Or-nE)
![image](https://private-user-images.githubusercontent.com/415439/253493581-24819486-00fa-4b79-9ac1-b17ad6586da9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDM5MzM2MTEsIm5iZiI6MTcwMzkzMzMxMSwicGF0aCI6Ii80MTU0MzkvMjUzNDkzNTgxLTI0ODE5NDg2LTAwZmEtNGI3OS05YWMxLWIxN2FkNjU4NmRhOS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjMxMjMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDIzMTIzMFQxMDQ4MzFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZDYwNzMzMjQ5YTIxMGMyZGUzMzQxZjQ1ZmUyNjI5MWUwMzlkMjY4MDI3OGExNWFmMjRkZWRhZjY4Y2RiOGIzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.CZFUdi8um4kGUp5u92ZpLKPEhst160AdTdhnxZyoTTw)
Maybe your system has fewer "versions" of Segoe UI installed thus picking another one than on my system?
Or maybe Windows 10 renders Zeta Resource Editor different than Windows 11?
Found out I checked "Override high DPI scaling behavior" box for ZetaResourceEditor.exe to "System (Enhanced)".
It was my fault 😅