Page turn area setting in Koreader

[crimsonsnow]

In Coolreader you can set touchscreen command for 9 separate areas. In my e-reader I set everything other than the bottom-middle area as next-page so that I can turn pages easily using both my right and left hand.

Is there any way to set similar page turn setup in Koreader? As far as I know in setting you can set x, y, and height, but I can only manage a big area on the right side for next-page and a very small area on the left side for previous-page.


Any setup to make both the rightmost and leftmost touch-screen area as next-page (and any other part as previous-page) will work too.

Thank you.

[Ken Maltby]

From /.adds/koreader/defaults.lua:


-- customizable tap zones(rectangles)
-- x: x coordinate of top left corner in proportion of screen width
-- y: y coordinate of top left corner in proportion of screen height
-- w: width of tap zone in proportion of screen width
-- h: height of tap zone in proportion of screen height
DTAP_ZONE_MENU = {x = 1/8, y = 0, w = 3/4, h = 1/8}
DTAP_ZONE_CONFIG = {x = 1/8, y = 7/8, w = 3/4, h = 1/8}
DTAP_ZONE_MINIBAR = {x = 0, y = 15/16, w = 1, h = 1/16}
DTAP_ZONE_FORWARD = {x = 1/4, y = 0, w = 3/4, h = 1}
DTAP_ZONE_BACKWARD = {x = 0, y = 0, w = 1/4, h = 1}
DTAP_ZONE_BOOKMARK = {x = 7/8, y = 0, w = 1/8, h = 1/8}
DTAP_ZONE_FLIPPING = {x = 0, y = 0, w = 1/8, h = 1/8}
DDOUBLE_TAP_ZONE_NEXT_CHAPTER = {x = 6/8, y = 0, w = 2/8, h = 2/8}
DDOUBLE_TAP_ZONE_PREV_CHAPTER = {x = 0, y = 0, w = 2/8, h = 2/8}

Luck;
Ken

[Alan_S]

Also, just to mention, it may be easier for someone (it is to me), you don't need to use 1/8, 1/16, 15/16 etc, you could use decimal values, like 0.9, 0.95, 0.1 etc.

Anyway, koreader really enables you to set your tap zones the way you like them to be. I'm pretty happy with my setup. Big area for next page, and small border areas for everything else, so basically I don't need to "aim" much for next page, only for other functions, which makes it easy, as next page is most common function, all others are rare and it is not big problem to pay a bit more attention.

[crimsonsnow]

Originally Posted by Ken Maltby

From /.adds/koreader/defaults.lua:


-- customizable tap zones(rectangles)
-- x: x coordinate of top left corner in proportion of screen width
-- y: y coordinate of top left corner in proportion of screen height
-- w: width of tap zone in proportion of screen width
-- h: height of tap zone in proportion of screen height
DTAP_ZONE_MENU = {x = 1/8, y = 0, w = 3/4, h = 1/8}
DTAP_ZONE_CONFIG = {x = 1/8, y = 7/8, w = 3/4, h = 1/8}
DTAP_ZONE_MINIBAR = {x = 0, y = 15/16, w = 1, h = 1/16}
DTAP_ZONE_FORWARD = {x = 1/4, y = 0, w = 3/4, h = 1}
DTAP_ZONE_BACKWARD = {x = 0, y = 0, w = 1/4, h = 1}
DTAP_ZONE_BOOKMARK = {x = 7/8, y = 0, w = 1/8, h = 1/8}
DTAP_ZONE_FLIPPING = {x = 0, y = 0, w = 1/8, h = 1/8}
DDOUBLE_TAP_ZONE_NEXT_CHAPTER = {x = 6/8, y = 0, w = 2/8, h = 2/8}
DDOUBLE_TAP_ZONE_PREV_CHAPTER = {x = 0, y = 0, w = 2/8, h = 2/8}

Luck;
Ken

Thank you for this! I got the rough idea for which variable to edit, but this exact list is definitely better to check what to change and to what.

Is the order of the setting affect the tap zone? (As in if we set the parameters and a zone belong to more than one command, does the last one override the previous one?

For an extreme example, if we set
DTAP_ZONE_FORWARD = {x = 1/4, y = 0, w = 3/4, h = 1}
DTAP_ZONE_BACKWARD = {x = 1/4, y = 0, w = 3/4, h = 1}
Do we end up not having a next-page area or previous-page area? If I infer from the original setting, the top one wins?
)

Originally Posted by Alan_S

Also, just to mention, it may be easier for someone (it is to me), you don't need to use 1/8, 1/16, 15/16 etc, you could use decimal values, like 0.9, 0.95, 0.1 etc.

Anyway, koreader really enables you to set your tap zones the way you like them to be. I'm pretty happy with my setup. Big area for next page, and small border areas for everything else, so basically I don't need to "aim" much for next page, only for other functions, which makes it easy, as next page is most common function, all others are rare and it is not big problem to pay a bit more attention.

Thank you! I can work with both, but I think fraction works better for me.

The ultimate ease in deciding the tap zones is both very helpful and overwhelming, you can tinker even for the 1/nth part of the screen (I guess if you have larger screen you can set area smaller than 1/16), but if you're not careful the possibility to mess something up is higher too.

[Frenzie]

Yeah, some kind of tap/gesture manager is one of those difficult long-term goals.

[Alan_S]

Originally Posted by crimsonsnow

I guess if you have larger screen you can set area smaller than 1/16

You can go as small as you want. And in case if area is too small for you, you can always edit file and correct to working values.

[favero_]

Is it possible to invert the page turn buttons too?

Thanks!

[NiLuJe]

@favero_: Top Menu > Gear Tab (I think? ) > Navigation > Invert page turn buttons

[geoslake]

Hi guys, that is not crystal clear to me.
I managed to set my forward/backward zones to my liking (bottom 2/3 is forward, top 1/3 is backward.
I would like to keep the bookmark gesture (touch the small bottom right corner region) and the swipe down or/and up to get the menu, and disable all of the other gestures.
Could someone please help me out ?

Thanks

[NiLuJe]

See this pretty picture for a visual aid.

All of these colored zones are individual DTAP_ZONE_* constants, manually tweakable in the Advanced settings menu (Tools > More tools > Advanced settings).

The only thing that has a slightly user-friendlier toggle are the four corners (in cyan), which you can disable (set to Nothing) in the Gesture Manager (Gear > Taps and gestures > Gesture manager).

If you want to *disable* some of the other regions, you'll have to set them to an empty rectangle (e.g., x=0, y=0, w=0, h=0).

Note that tap and swipe zones use the same setting, so you can't, say, disable taps but allow swipes, or vice versa.
With a singular exception: the top and bottom menus (Gear > Taps and Gesture > Activate menu).