maemo.org Bugzilla – Bug 2714
PDF Reader: Page up should go to Bottom of Previous Page (instead of Top)
Last modified: 2012-03-24 11:43:55 UTC
You need to
before you can comment on or make changes to this bug.
At the top of a page, hitting the top four-way key should
scroll up to the bottom of the previous page.
At present it goes to the top of the previous page.
(See also Bug 2703.)
In Adobe Reader on the desktop, you can display the PDF either in "Single Page"
or "Single Page Continuous" mode. It seems to me that the Maemo PDF reader is
always operating in "Single Page" mode and "Single Page Continuous" should be
added along with the option for the user to choose their preferred Page Display
mode (ie. either Single Page or Singe Page Continuous).
Created an attachment (id=906) [details]
PDF Reader -Paging up goes to top of Prev Page
Now hitting the top four-way key should scroll up to the bottom of the previous
page.And there is a enhancement that ,i have add a "display page continue "menu
option in the "View" menu,that when click it ,we can drag the pdf vertical
srcollbar to jump to the top of next page or the bottom of the previous page.
Hua.Yang: Can you please provide a clean patch without any indention changes,
without your commented debug code, and without clutter lines like
> -void on_screen_scroll(GtkAdjustment * adjustment, gpointer user_data);
> +int on_screen_scroll(GtkAdjustment * adjustment, gpointer user_data);
Please explain why this change is needed.
Please also provide a ChangeLog entry diff explaining what the patch exactly
Hua.Yang: Can you please provide a clean patch as described in my last comment?
Also note that the 3rd party port of Evince provides this functionality:
Fremantle Spec does not clearly define the behaviour, it just says
"The user presses the “next page” or “previous page” button and the application
switches the page. The user presses the “first page” or “last page” button and
the application switches the page."
So I assume that there is no change in behaviour for Fremantle.
...and hence it's simply not defined, which makes this an enhancement request,
though a VERY useful one.
Hua.Yang: Can you please provide a clean patch?
This is still valid in Fremantle. --> Updating version field.
Marking patches of interest to Diablo (Maemo4) community updates, please excuse
The Maemo 5 User Interface and Maemo 5 platform components (e.g. libraries)
used for the N900 are considered stable by Nokia and it seems that there are no
plans for official updates currently, hence nobody plans to work on this
(And in case you feel like discussing this situation: Nokia Customer Care or
http://talk.maemo.org would be the place to do so as you will not reach Nokia
officials in this community bugtracker - though all of this is really no news.)
Reflecting this status by setting RESOLVED WONTFIX for this
enhancement/wishlist request (see
https://bugs.maemo.org/page.cgi?id=fields.html#status for status explanations).
There is a small chance for issues in those Maemo components that are open
source: Contributed patches could be included and made available in the Maemo 5
Community CSSU updates.
The Maemo CSSU project is run by a small team of volunteers; see
http://wiki.maemo.org/CSSU for more information.
So in case that you can provide a patch that fixes the reported problem, please
feel encouraged to file a request under
Please note: The Maemo CSSU project is not related in any way to Nokia.
( Tag for mass-deleting bugmail: [cleanup20120324] )