[Okular-devel] [okular] [Bug 316890] New: Intelligent automatic reload

[Dennis Nienhüser]

https://bugs.kde.org/show_bug.cgi?id=316890

            Bug ID: 316890
           Summary: Intelligent automatic reload
    Classification: Unclassified
           Product: okular
           Version: 0.16.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: PS backend
          Assignee: okular-devel at kde.org
          Reporter: earthwings at gentoo.org

I'm working on a larger PDF file produced by kile/pdflatex which takes about 30
seconds to build. When I initiate a build in kile, the PDF document gets
cleared immediately (the PDF file is truncated) and only shown again 30 seconds
later after the build is finished and the new PDF file complete. Alternatively
I can switch off auto-reload in okular, but have to reload the document
manually later on.

Instead I'd like okular to reload the document automatically, but only when the
build is finished.

My guess what is happening in auto reload mode currently is the following:

1) PDF file is ok, shown in okular
2) Initiate build, pdflatex truncates pdf
3) okular notices file change, tries reload. File is not complete, nothing
shown
4) pdflatex writes some chunks to the file.
5) The pdf might not be complete, back to 3). Otherwise okular displays the new
file

What I'd find more convenient would be
1) PDF file is ok, shown in okular
2) Initiate build, pdflatex truncates pdf
3) okular notices file change, tries reload. File is not complete. Old file is
still shown, along with a "file vanished on disc" indicator in the user
interface
4) pdflatex writes some chunks to the file.
5) The pdf might not be complete, back to 3). Otherwise okular displays the new
file, removes "file vanished on disc" indicator

The main difference is that I can continue reading the (outdated, but still
useful) PDF while it is updated.

Is that doable or would that break e.g. loading of other pages which are not in
memory?

-- 
You are receiving this mail because:
You are the assignee for the bug.