search

DJDoubleD / QobuzDownloaderX-MOD

Downloads streams directly from Qobuz. Experimental refactoring of QobuzDownloaderX by AiiR
GNU General Public License v3.0
478 stars 16 forks source link

bottom part cannot be seen on 150% scaling #48

Closed AntiSelosAcademy closed 1 year ago

AntiSelosAcademy commented 1 year ago

I have a 1080p laptop with windows 11 that uses 150% scaling and the bottom half gets cut off force it to use fix scaling.

Screenshots

With fix scaling Screenshot 2023-08-19 183432 Without Fixed scaling Screenshot 2023-08-19 184328

DJDoubleD commented 1 year ago

I don't have a Windows 11 system to test this on, this might be a limitation of the aging Winforms platform. Windows 10 seems to handle scaling just fine. Is there maybe a possibility to launch the app using compatibility settings on windows 11?

AntiSelosAcademy commented 1 year ago

I guess so, windows scaling has so many problems.

explorer_Q9vAJj0Fb3

I have to uncheck these just for the app to display correctly. And it looks blurry, but usable.

DJDoubleD commented 1 year ago

I guess so, windows scaling has so many problems.

explorer_Q9vAJj0Fb3

I have to uncheck these just for the app to display correctly. And it looks blurry, but usable.

Ah, I misunderstood your original question and didn't realize that when you said "use fix scaling", you meant the High DPI setting to "fix scaling" instead of using a fixed scaling percentage of 150%...

This is also far from perfect on Windows 10 as without the High DPI scaling override option checked, the labels get more blurry the higher the scaling is set. But the app seems to keep full functionality. And when enabling the different options to override the high dpi scaling, the app either doesn't get scaled at all or breaks as soon as the tag settings at the bottom are opened...

I have read up on this some more and it seems pretty clear that, in order to get correct and clear (crisp) scaling on any Windows version, the entire application would basically have to be rewritten. I'm afraid that's out of scope of this project/repo and you have already pointed out a less then perfect but workable solution. So I'll have to close this issue.