View Single Post
Old 08-06-2019, 01:30 PM   #51
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,939
Karma: 6361444
Join Date: Nov 2009
Device: many
Okay just pushed a fix for spurious load impacting m_pendingLoadCount which in turn can prevent ExecuteCaretUpdate from running (which repositions PV based on the location of CodeView).

This fix will appear in the upcoming release of Sigil. If further problems are detected after the new release, we can re-enable debug messages again and hopefully get any remaining nits tracked down.

Right now we have fixed syncing loss in Linux using Qt 5.9.X and 5.10.X, fixed syncing loss due to minimize/restore, fixed syncing loss due to overly speedy find/replace causing PV load collisions, and now fixed syncing loss due to spurious load completed signals.

Hopefully this will do the trick.
KevinH is offline   Reply With Quote