Version: (using KDE KDE 3.5.3) Installed from: Compiled From Sources When KPDF is loading a new page, it usually takes seconds before the final rendering appears, showing nothing but a diagonal cross across the page and sometimes a magnified version of the thumbnail preview -- interrupting the flow of reading. However, this is not too useable as you cannot start reading the content unless it is fully rendered. Acrobat Reader and KGhostview take another way which not only makes them "feel" faster but also enables the user to start reading before all of the page has been rendered: They immediately output the rendering to the screen, even if the page is still being processed. As most pdf-documents are laid out in reading-order, the upper part of the page (usually the position one starts reading, at least LTR-readers) will be shown virtually immediately, thus enabling the reader to start reading, while the later parts are incrementally displayed as rendering proceeds. It is to be expected that the reader needs much longer to read the text than the algorithm needs to process the page, hence incremental rendering would be worthwile. Therefore I propose that KPDF be enhanced with an incremental rendering mode, just like kghostview and AR do.
I think this is a duplicate of #126806 (or at least both could be addressed together).
Of course not, Kevin, they are totally different issues. I don't see how configuring the prerendering cache of aggressive mode has something related to the fact of showing incrementally a page (note: for *every* memory configuration) while it's being rendered.
Thank you for your bug report or feature suggestion. The "KPDF" application is no longer maintained, and all tickets are now closed. We recommend to switch to the "Okular" application. Due to the high number of bugs/suggestions in "KPDF" we are not able to go through all of them and verify if they are still valid in "Okular". That's why are we asking you to help us by checking if your bug/suggestion is still valid in Okular and if it still is opening a new bug/suggestion against it. Thank you for your effort in making KDE better :) (This is an automatic message from the KDE bug triaging team)