Summary: | horizontal continuous scrolling | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Ansa <ansa.ansa> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | azrdev, gerion.entrup, peter.meilstrup, ryan, stefan.bruens |
Priority: | NOR | ||
Version: | 0.19.3 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=371904 https://bugs.kde.org/show_bug.cgi?id=439417 |
||
Latest Commit: | Version Fixed In: |
Description
Ansa
2015-02-07 22:28:01 UTC
*** Bug 414796 has been marked as a duplicate of this bug. *** I don’t think extending the Overview column limit is the right way. What should the limit be? Imagine you read an A4 format flyer with 6 pages, so you are happy to turn on Overview mode and Fit Width. Then you open your favorite instruction set summary, and get one horizontal line of pages, which are 0.05px height each. This will be invisible, so it looks like Okular is broken. Requesting all 25,000 page pixmaps at once would probably indeed crash Okular.
> + provide "Zoom: fit height" option (similar to "Zoom: Fit width" and "Zoom: Fit page")
Fit Width wouldn’t make sense for horizontal continuous mode (for the explained reason), so Fit Width and Fit Height could be the same option, right? (In the sense of Zoom to Fill)
*** Bug 390709 has been marked as a duplicate of this bug. *** Continuous horizontal scrolling is an important feature for me. It is available in PDF-XChange, which I pay for and use mainly because of this feature. However, PDF-XChange is a commercial application for Windows only. My primary use case is reading and adding annotations to scientific journal articles. Typically, these have a two-column layout that makes vertical scrolling awkward. In contrast, continuous horizontal scrolling: - always places related columns adjacent to each other; - allows use of the full horizontal space of a wide screen, making it easier, for instance, to view a graph or table on one page while referring to related text on another page; - provides the flexibility to view even-odd page-pairs (with the even-numbered page on the left); and - the reading experience is more natural than vertical scrolling (for material that represents printed media), because left/right scrolling moves in the same direction as a physical page-turn. In PDF-XChange, rolling the mouse wheel up/down scrolls left/right (or right/left) if the page view is zoomed to page height or less. When the zoom is greater than full page height, the wheel changes to up/down scrolling. Left/right scrolling is still possible with a tilting mouse wheel or using the grabber (pan tool). Continuous horizontal scrolling is remarkably useful, yet not found in any other PDF application, to my knowledge, other than PDF-XChange. It would be great to see this added to Okular. (In reply to Ryan from comment #4) > Continuous horizontal scrolling is remarkably useful, yet not found in any > other PDF application, to my knowledge, other than PDF-XChange. Correction: the PDF viewer in Firefox (94.0.1) includes horizontal scrolling. (In reply to David Hurka from comment #2) > Fit Width wouldn’t make sense for horizontal continuous mode Fit Width should fit the width of exactly one page -- the current page -- regardless of its orientation, and not the total width of a multi-page document. > Fit Width and Fit Height could be the same option This would depend on size and orientation of the monitor and page displayed. With a 16x9 monitor, for example, in landscape orientation, vertical space is usually the constraint (if the page is of A4 or letter size and in portrait orientation), so Fit Page and Fit Height would produce the same result. With the monitor in portrait orientation, horizontal space would become the constraint, meaning that Fit Page and Fit Width would now produce the same result, whereas Fit Height would fill the screen vertically, leaving one or both sides of the page out of view. *** Bug 443909 has been marked as a duplicate of this bug. *** |