Hi,<div><br></div><div>Feature Request: Is it easy enough for the previewer to be made able to go in and out of grey-scale presentation and colour mode please?</div><div><br></div><div>Bug or Feature?: I've noticed that if I open a pdf first (made via TeXworks), and use click-sync in that pdf, that the .tex editor opens as expected, but also an extra copy of the .pdf as well.</div>
<div><br></div><div>Then if I click-sync in the newly opened .tex editor, both copies of the .pdf yellow highlight to the correct place. </div><div><br></div><div><a href="http://dl.dropbox.com/u/13401476/TeXworks/double_pdf.jpg">http://dl.dropbox.com/u/13401476/TeXworks/double_pdf.jpg</a></div>
<div><br></div><div><img src="cid:ii_13314846bda7b03f" alt="double_pdf.jpg" title="double_pdf.jpg"></div><div><br></div><div><br></div><div>Paul</div><div><div>----- configuration info -----</div><div>TeXworks version : 0.5r862 (official)</div>
<div>Install location : G:/latexportable/LaTexUtils/TeXWorks/texworks/TeXworks.exe</div><div>Library path : G:/latexportable/LaTexUtils/TeXWorks/texworks/config\</div><div>pdfTeX location : G:/LaTeXPortable/LatexUtils/MikTex2.9.3927-Portable/miktex/bin/pdftex.exe</div>
<div>Operating system : Windows XP Professional Service Pack 3</div><div>Qt4 version : 4.7.3 (build) / 4.7.3 (runtime)</div><div>------------------------------</div><div><br></div><br><div class="gmail_quote">On 8 October 2011 04:02, Charlie Sharpsteen <span dir="ltr"><<a href="mailto:chuck@sharpsteen.net">chuck@sharpsteen.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Sun, Sep 25, 2011 at 5:34 PM, Charlie Sharpsteen <span dir="ltr"><<a href="mailto:chuck@sharpsteen.net" target="_blank">chuck@sharpsteen.net</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Bad news on the partial render front---looks like Poppler just can't do it---at least not in an efficient manner. Every page render request, regardless of the backend that is used, causes Poppler to re-parse the entire page rather than parsing once and then working off of some sort of cache. The parsing requires the most time and processor power so splitting a large pixmap up into tiles basically multiplies the rendering time by the number of tiles that are used.</div>
<div><br></div><div>Discussions and bug reports in other projects:</div><div><ul><li>Evince: <a href="https://bugzilla.gnome.org/show_bug.cgi?id=303365" target="_blank">https://bugzilla.gnome.org/show_bug.cgi?id=303365</a></li>
<li>Okular: <a href="https://bugs.kde.org/show_bug.cgi?id=148527" target="_blank">https://bugs.kde.org/show_bug.cgi?id=148527</a></li>
</ul><div>I think Okular's method of dealing with the problem makes the best of a bad situation--once the amount of pixels in a rendering request exceeds a certain value, they just ignore it. So the user can zoom in as much as they like, but after a point things just stay fuzzy. This would be pretty easy to implement in our current rendering setup.</div>
</div><div><br></div><div><br></div><div>If only there was an open source PDF library that provided threadsafe partial rendering...</div><div><br></div><font color="#888888"><div>-Charlie</div>
</font></blockquote></div><br></div><div><br>I have to retract the above statements---Poppler can indeed do partial rendering in a more efficient manner than full page rendering.</div><div><br></div><div>I just finished modifying the viewer prototype so that it splits pages into tiles that are 1024x1024 pixels and renders the tiles that are currently showing in the viewport. Memory usage is way down---I can zoom past 10,000% and the viewer doesn't even show up in my 10 ten memory-intensive processes.</div>
<div><br></div><font color="#888888"><div>-Charlie</div>
</font></blockquote></div><br></div>