Thread: Sigil slow
View Single Post
Old 04-21-2022, 06:29 PM   #7
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,761
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by DiapDealer View Post
That's good to hear!

I honestly don't know why INI file corruption is so prevalent, but I'm fairly confident it's a Qt thing.
. . .
I run five programs that I know use QT (there may be others) - Sigil, Calibre, Falkon, qBitborrent, and Malwarebytes.

The first three seem to suffer inexplicable window geometry problems on Windows and Linux. And I'm pretty sure they each use QT's browser widget, I suspect the other two don't.

If the geometry bytearrays were kept in a separate config file (e.g. geometry.ini/json), that would allow it to be nuked with impunity without loss of other settings. I have no idea if or how easy that would be to implement.

FTR - I have not experienced any of these problems, but I've exorcised geometry bytearrays from several calibre and one sigil configuration for other people.

BR

Last edited by BetterRed; 04-21-2022 at 07:41 PM.
BetterRed is offline   Reply With Quote