View Single Post
Old 03-16-2024, 02:51 PM   #61
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,602
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
I say we add the nodirectwrite platform argument like we do altgr (except with no user preference involved) to force the gdi font backend for now. We can revisit removing it when the DirectWrite backend proves to be more complete.

If we don't do something, we'll be chasing mystery windows crashes as more users encounter embedded woff fonts on scaled displays. And I'm for the path of least Qt patching.

EDIT: for the record... adding the "fontengine=freetype" platform option seems to accomplish the same thing as nodirectwrite. It also eliminates any of the QWindowsFontDatabase::fontEngine warnings encountered when using nodirectwrite.

Last edited by DiapDealer; 03-16-2024 at 03:22 PM.
DiapDealer is offline   Reply With Quote