View Single Post
Old 06-07-2020, 05:13 AM   #8
tourneur
Zealot
tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.tourneur ought to be getting tired of karma fortunes by now.
 
Posts: 111
Karma: 385602
Join Date: Aug 2019
Location: The Netherlands
Device: Kobo Libra
Quote:
Originally Posted by stumped View Post
what level of magical programming can tell the difference between turning a page in multi page options, as opposed to turning a page in a book

it's a ludicrous idea

you are wanting code that knows " why" you just tapped.....

good luck writing your patch - I am done here
Code cannot tell when you are in a menu or in reading mode? And you still have interface buttons for paging within menus, if that was even necessary.

OP was clearly talking about disabling "tap to page turn" in reading mode. Effectively extending the menus tap zone in reading mode to the entire screen, and removing the page turn tap zones. If you can move the tap zones around like you can right now you can obviously also remove the page turn zones altogether without affecting anything else.
tourneur is offline   Reply With Quote