We'll certainly look into that commit, but I don't want to start conflating different issues. A major performance issue was reported by a few after we released 0.9.11 (the first version to update Qt/QtWebKit and Python in quite some time). I'd like to make sure we've resolved THAT issue before we start looking at later memory foot-print reducing strategies and their impact.
Quote:
|
@DiapDealer: Get from AppVeyor history 0.9.13-100 and 0.9.13-101.
|
No need. I'm always running the latest Appveyor build on one machine or another (currently 0.9.13-131). Which contains the commit in question. Making editing with Preview
uncomfortable, I get. We'll work on that. But that's not a performance issue or a slow down in Sigil's response time (or a "not responding" situation). Which is what we're mainly trying to address.
So my question to theducks is simply this: is Sigil 0.9.13
itself slowing down for you, or is it simply doing something differently with regard to Preview synchronization that you find too annoying to continue using?
I'm not dismissing this issue. I just want to make sure it's not getting lumped in with the general performance/resource problem some are experiencing. Thanks, @BeckyEbook for providing a clear explanation of the issue being experienced. I appreciate the research.
EDIT: one doesn't even need to use the "Find" button. Clicking in the text in Code View will cause the jump to the top of the page before scrolling back to the correct position. But only if there's embedded fonts or images in that file. The text-only TOC, for instance, doesn't do any of that "flashing" when Preview is being synchronized to Code View.