Annotation works up to beginning of page 684 (0.4.7)
Brought to you by:
andreasb123,
auroux
Running xournal 0.4.7 installed from repositories on linux mint 15.
Annotation works nicely up to beginning of page 684, where it suddenly stops at a horizontal line. I have some 1100 more pages to go on my doc :D
Suspect nothing wrong with the original PDF (downloadable on http://assets.jw.org/assets/a/nwt/nwt_E/nwt_E.pdf), since all the other pages are annotatable.
Tried annotating with different tools, all stop at the same point.
I think the issue is an overflow with the vertical coordinates of the pointer click events when the y coordinate relative to the top of the scrollable area goes beyond precisely 1 million pixels. This may be a limit set in GTK+ (not sure?).
Aside from zooming out to fit the whole document in 1 million pixels, there's an easy workaround: View -> One page.
Also note that you'll probably use insane amounts of RAM annotating such a huge PDF document in xournal, since all visible PDF backgrounds are kept in memory -- it might be wiser to break it into smaller chunks.
Denis
Cool I'll try that. It's still a bug though. ;)
Yes. I have only 16GB, but it works quite well anyway. Main contributing factor probably is that the PDF is mostly "real" text, not images. Only problem is, as mentioned, I can't annotate below 1Mpx :)
I think the issue is an overflow with the vertical coordinates of the
pointer click events when the y coordinate relative to the top of the
scrollable area goes beyond precisely 1 million pixels. This may be a
limit set in GTK+ (not sure?).
Aside from zooming out to fit the whole document in 1 million pixels,
there's an easy workaround: View -> One page.
Denis
On 10/12/2013 03:09 PM, Arno Teigseth wrote:
--
Denis Auroux auroux@math.berkeley.edu
University of California, Berkeley Tel: 510-642-4367
Department of Mathematics Fax: 510-642-8204
817 Evans Hall # 3840
Berkeley, CA 94720-3840
Related
Bugs:
#132Million pixel limit was in our code, not in GTK. Oops, my bad. Release 0.4.8.2016 is up to date with cvs/git repositories, and should include a fix for this bug. Please reopen if problems persist with 0.4.8.2016 or with the current cvs/git code.