After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 624447 - Triple page mode for optimal use of wide-screen displays
Triple page mode for optimal use of wide-screen displays
Product: evince
Classification: Core
Component: general
Other All
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Reported: 2010-07-15 12:12 UTC by oliver
Modified: 2018-05-22 13:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description oliver 2010-07-15 12:12:26 UTC
The now ubiquitous 16:9 screens are capable of displaying three pages of typical print material (A4 or letter sized pages, technical reports, etc.) side by side.  It would often be useful to make use of all the available space for onscreen reading of such material. 

This could be done in several ways: 

* A "Triple" mode which displays three pages ("fit to visible", see or better manually positioned for maximal zoom level at which continuous reading is possible), page up/down would only go one physical page up or down so that any three consecutive physical pages could be positioned on-screen for continuous reading.  

* Really cool would be a "horizontal continuous mode" where one could continuously move, with the mouse, a horizontal band of vertically maximized pages, left or right.  (Personally, I think this would be much more useful than the vertical scroll mode ("Continuous") which I almost always switch off because the physical distance between the last relevant line of one page and the first relevant line, excluding footers and headers, of the next page is usually far to big for documents which have been laid out for printing.)
Comment 1 GNOME Infrastructure Team 2018-05-22 13:56:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: