View Single Post
Old 08-01-2025, 12:31 PM   #25
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by BeckyEbook View Post
I think everything is fine right now (in the master branch), and I sincerely appreciate that.
For the majority of users, file dialogs are safe, and those who take risks have an environment variable. Obvious that they are doing so with full awareness of the potential risks, such as a Sigil crash.
The problem is they will blame Sigil for the crash when it is in fact a Qt crash and from the looks of it primarily related to insufficient testing on their part. When you combine macOS native QFileDialog crashes with Windows native QFileDialog crashes (not even counting Unix/Linux ones) there has been serious Qt crashing bugs in more than 50% of the Qt versions we have tried (and those are chosen to be the more stable Qt 6.x.y with y >= 2).

Qt needs to stop their mad push for new features and instead focus on proper testing and bug squashing. But they reserve that for commercial $ licenses only. We open source users are just their guinea pigs!
KevinH is online now   Reply With Quote