View Single Post
Old 04-15-2024, 09:01 AM   #64
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: 28,701
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Qt light/dark on Windows is getting better, but it's still quite the crap-shoot. Fusion is still the recommended base for style changes.

I can do some experimenting to see if going with a fully Windows/user-chosen dark mode is feasible (I'm not sure if Windows on-the-fly switches are supported yet where Qt is concerned, to be honest. The lack of a Qt api to detect theme changes). There's also differences between Windows 10 and Windows 11 behavior. We should have some options since moving to Qt6.6, but there's no guarantee that whatever dark theme is automatically chosen by Windows/Qt will be compatible with the default colors/highlighting for Code View.

Some good (and by good I mean confusing and self-contradicting!) reading on the subject here: https://www.qt.io/blog/dark-mode-on-...11-with-qt-6.5

Most Linux users rely on platform themes and qtct/kvantuum to style their Qt applications. The dark mode we currently make available to Linux (same as the Windows one) if they set an environments variable, should be considered a last resort, in my opinion

Last edited by DiapDealer; 04-15-2024 at 09:40 AM.
DiapDealer is offline   Reply With Quote