Summary: | fast turning pages of pdf files faster than the content is displayed | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Salazar <salazar666> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | maui.bugzilla |
Priority: | NOR | ||
Version: | 0.6.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Salazar
2008-03-16 14:08:05 UTC
> Next thing is, that even if you have assigned the keys or feel ok with the
> descibed behave, Okular turns the PDF pages so fast, that they will not be
> displayed anymore until you stop pressing the key.
Why should that be a bug? If you keep then next page shortcut pressed, it just follow what -you- want, that is going ahead fast.
Even acroread just shows a page in a while: with a 300+ pages document and keeping the next page shortcut pressed from page 1 up to the end, it displayed just 3 pages, and the other ones not even the frame.
Yes, you're right, also acroread shows not each single page if you scroll through the PDF fast. But in acroread you'll never see blank pages. Compared with this, Okular shows only the page frames, but is not able to display the page content so fast. So you will see only the first (maybe the second) and the last page of your 300+ pages document. The pages inbetween will only be displayed as empty frames. Pino Toscano schrieb: [bugs.kde.org quoted mail] Now I remembered ... the Windows Version of Adobe Acrobat is showing each single page by going ahead fast. In my job I often work with large PDF files and it's such a helpful thing if you can browse quickly for getting an overview. *** Bug 194327 has been marked as a duplicate of this bug. *** |