View Single Post
Old 08-18-2022, 11:46 PM   #9
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,053
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Comfy.n View Post
I think I've seen that oddity too, then I played with all those High DPI settings and environment variables, and all is well now. What suited my use case was disabling QT scaling, as I detailed here. As for the HiDPI override settings, what works well more often for me is "scaling performed by application"
Disabling QT's high DPI didn't seem to help, neither did setting scaling to performed by application. Basically, I had have Windows override QT to work around the issue.

At least with the workaround, I don't need to worry until the next update to QT 6.

Also note that this also worked with the Preview pane issue I was having with Sigil though the Sigil version I'm running is still using QT 5.

Last edited by DNSB; 08-18-2022 at 11:49 PM.
DNSB is offline   Reply With Quote