View Single Post
Old 07-19-2022, 12:12 AM   #299
Comfy.n
want to learn what I want
Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.Comfy.n ought to be getting tired of karma fortunes by now.
 
Posts: 1,665
Karma: 7908443
Join Date: Sep 2020
Device: none
Thumbs up

Quote:
Originally Posted by thiago.eec View Post
I noticed this problem with the first beta launched months ago. I had completely forget about this until you mentioned it now. Here is my original post about this.

Apparently, QT has trouble when you use a non integer scale factor (I use 125% on my Windows 10 machine). There are multiple ways to correct this using an environment variable (see @Quoth's post on the other page). In addition to what he suggested, I can confirm that any of this variables work too:
Code:
QT_SCALE_FACTOR_ROUNDING_POLICY = Round
QT_ENABLE_HIGHDPI_SCALING = 0
Only one of the above is necessary.

Source:
https://doc.qt.io/qt-6/portingguide.html#high-dpi
https://doc.qt.io/qt-6/highdpi.html#...able-reference
Thank you so much for that input.

Using that second variable has fixed undesired Calibre/QT scaling changes on my side (Winblows Tense, 1920 x 1080 laptop screen, forcibly set to custom 125% scaling in order to bypass MS sharpness incompetence).

For those that face this issue, it might be of help to know where to insert that line: here.
Comfy.n is offline