<table><tr><td style="">aacid added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D9328" rel="noreferrer">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D9328#179878" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">D9328#179878</a>, <a href="https://phabricator.kde.org/p/michaelweghorn/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@michaelweghorn</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>I tested this a bit and find it really nice that rendering of the actual page (rather than the thumbnail) usually starts at once when re-rendering is needed (e.g. when zoom level is changed).<br />
Also, closing Okular now works fast, even if rendering is still in progress. (The shell prompt is shown almost immediately after closing Okular when it was started from the command line.)</p>
<p>While the above is true most of the time, it happens from time to time that rendering does not start at once.<br />
I can reproduce this e.g. the following way:</p>
<ul class="remarkup-list">
<li class="remarkup-list-item">open a file that takes long to render</li>
<li class="remarkup-list-item">zoom "one step" in and out every few seconds (using the mouse wheel)
<br /><br />
While re-rendering is triggered most of the times at once, the page sometimes remains "blank" for more than 30 seconds. In those cases where the page is "blank", it also takes long for the Okular process to finish when closing the program at that point in time.
<br /><br />
I (temporarily) uploaded a screencast here: <a href="https://ombx.io/4SDa42mm" class="remarkup-link" target="_blank" rel="noreferrer">https://ombx.io/4SDa42mm</a></li>
</ul></div>
</blockquote>
<p>That seems like a bug, it shouldn't do that, i'll try to reproduce here.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Another thing I realized is that re-rendering is now triggered every time the zoom level is changed.<br />
Without this change, rendering the page is sometimes just continued at the place where it was before changing the zoom level (which results in the final page appearing earlier when no re-rendering is needed).</p></blockquote>
<p>Yes and no, what happened before is that after the first rendering finished a second one would start with the correct quality for the current zoom, but since the first one was probably "good enough" you got a scaled version while the second one was rendering, which sometimes it may be good, some other times it may be ultra pixelated, now we just cancel the first one and start the second one right away, so the time to "best/correct rendering" is shorter but the time to "something renderer" is a bit larger. I do think that this approach is better.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R223 Okular</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D9328" rel="noreferrer">https://phabricator.kde.org/D9328</a></div></div><br /><div><strong>To: </strong>aacid<br /><strong>Cc: </strong>michaelweghorn, ngraham, Okular, gassaf, aacid<br /></div>