Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

600: Use Volume buttons to move through history #31

Closed
GoogleCodeExporter opened this issue Mar 22, 2016 · 5 comments
Closed

600: Use Volume buttons to move through history #31

GoogleCodeExporter opened this issue Mar 22, 2016 · 5 comments

Comments

@GoogleCodeExporter
Copy link

Hi,

first of all, a big thank you!
This is an enhancement request, but I am not able to change the issue type...
It would be nice, if there was an option in key bindings, to use the volume 
buttons to move back and forth in the history of a book. I had this in my good 
old prs505 and miss it terribly.

Thank you
Sven

Original issue reported on code.google.com by opitzs@gmail.com on 25 Nov 2010 at 9:55

@GoogleCodeExporter
Copy link
Author

Adapt StandardActions.

Original comment by msukhias...@gmail.com on 26 Nov 2010 at 4:37

  • Changed title: 600: Use Volume buttons to move through history
  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Original comment by msukhias...@gmail.com on 26 Nov 2010 at 12:20

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by msukhias...@gmail.com on 28 Nov 2010 at 9:53

  • Changed state: Done

@GoogleCodeExporter
Copy link
Author

Hello. 
Those binding keys 
-history next 
-and history previous 
doesn't work actually on prs 650.

The others keys shortcut works fine (open TOC,...)

Original comment by visierantoine@gmail.com on 23 Oct 2011 at 9:59

@GoogleCodeExporter
Copy link
Author

They should work, and they do work on my 650 (and presumably on many others, 
since this feature was added a long time ago). If you can provide very precise 
steps to reproduce what you are seeing, please create a separate issue for it.

Original comment by quisvir on 23 Oct 2011 at 11:03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant