View Single Post
Old 06-01-2025, 11:02 AM   #11
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: 9,089
Karma: 6379704
Join Date: Nov 2009
Device: many
Again, Sigil 2.5.0 had a bug that made it incorrectly sync to the top of file. That is why you saw your error messages more in Sigil 2.5.0. Please try the exact same test in the exact same epub on Sigil 2.4.2. It should act like Sigil 2.5.1, not Sigil 2.5.0 when it comes to syncing behaviour as that is the code we reverted to.

If Sigil 2.4.2 somehow syncs to the error message at the top, please let me know and I will try to look into what else changed between Sigil 2.4.2 and Sigil 2.5.1 that might change the behaviour. Unfortunately since 2.4.2 there has been a large number of changes, even Qt changes that could be a culprit.

Nothing from the Sigil 2.5.0 to Sigil 2.5.1 other than the reverted whitespace to top fix) should have impacted that behaviour (same Qt, etc)

Last edited by KevinH; 06-01-2025 at 12:21 PM.
KevinH is offline   Reply With Quote