View Single Post
Old 09-16-2025, 01:16 PM   #6
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: 29,141
Karma: 211348980
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Sigil 2.6.2 is fine. It's still using Qt6.8.2. That version ran fine on the same machine I was testing on too. It wasn't until I installed a beta build of Sigil with Qt6.9.2 that my version of the runtime was insufficient.

I will say that it was a CI-built version of Sigil, so it's entirely possible it was the version of Visual Studio used to compile Sigil that caused the problem. But the fact of the matter is: the version of Visual Studio installed on github's action runner images is eventually going to be the version I use to make Sigil release builds on my local machine. So it's still only a matter of time before it becomes a factor.

Last edited by DiapDealer; 09-16-2025 at 01:21 PM.
DiapDealer is offline   Reply With Quote