Bug 145995 - gpdf's full screen mode fails to scale content to fit
Summary: gpdf's full screen mode fails to scale content to fit
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gpdf
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-24 16:39 UTC by Alexandre Oliva
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-11 17:54:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexandre Oliva 2005-01-24 16:39:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
xpdf -fullscreen doc.pdf will scale the document so as to fill the
screen (or at least take up all of one of the dimentions).  With gpdf,
it appears to be impossible to obtain the same effect: even if you
choose one of the `fit' options and then enter full screen mode, the
fit won't be for full screen, but rather for the original window, and
I don't see how to select the `fit' options while in full screen mode.

Version-Release number of selected component (if applicable):
gpdf-2.8.2-2.2

How reproducible:
Always

Steps to Reproduce:
1.Open a pdf document
2.Choose any of the `fit' options
3.Choose full screen mode

Actual Results:  Entering full screen mode won't cause the document to
be refit into the screen size; it will retain the size selected while
in a smaller window.

Expected Results:  It should refit for full screen.

Additional info:

Having a number of presentations in pdf format, designed to be
displayed in full screen mode with xpdf, if xpdf is to go away, it
would be nice if gpdf could display them just as nicely.

Comment 1 Alexandre Oliva 2005-03-11 17:54:40 UTC
evince in the development tree can handle them pretty well.  gpdf is
gone, so...


Note You need to log in before you can comment on or make changes to this bug.