| 
			
			 | 
		#1 | 
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 8 
				Karma: 10 
				Join Date: Mar 2021 
				
				
				
				Device: Kindle PW3 
				
				
				 | 
	
	
	
		
		
			
			 
			
			Hello everyone, 
		
	
		
		
		
		
		
		
		
		
		
		
	
	I'm trying on changing the next and previous tap zones to the following: 1 wide zone for the next page and 1 smaller zone right smack in the middle for the previous page ![]() The problem is it at the overlapped zone, the next page is being triggered instead of the previous page. Is there a way to set the z index of the tap zones?  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#2 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Not without code changes. IIRC, Next is indeed over Prev (on the basis that it's a much more common occurrence than Prev  
		
	
		
		
		
		
		
		
		
		
		
		
		
			 ).c.f., registerTouchZones @ frontend/apps/reader/modules/readerrolling.lua (reflowable documents) & frontend/apps/reader/modules/readerpaging.lua (non-reflowable documents). Last edited by NiLuJe; 04-17-2021 at 05:39 PM.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| Advert | |
| 
         | 
    
| 
			
			 | 
		#3 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,874 
				Karma: 10700629 
				Join Date: May 2016 
				Location: Canada 
				
				
				Device: Onyx Nova 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I set the whole screen to be a next page button (except for the middle which brings up the menu), and used swipe to page back. I rarely do previous page. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	https://www.mobileread.com/forums/sh....php?p=3930863 Android version: https://www.mobileread.com/forums/sh...d.php?t=325088  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#4 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Right, that's another viable approach, as swipes > taps (in terms of gesture detection, I mean. I hate swipes ^^). 
		
	
		
		
		
		
		
		
		
		
		
		
		
			(Note that, unlike the tap zones Z order discussed above, that's a general rule: detecting a gesture requires a finger up event, and if the finger moved far enough, that makes it a swipe instead of a tap, so, by definition, swipes > taps). Last edited by NiLuJe; 04-17-2021 at 02:38 PM.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#5 | ||
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 8 
				Karma: 10 
				Join Date: Mar 2021 
				
				
				
				Device: Kindle PW3 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 Thank you for pointing me to the right lua file! Quote: 
	
  | 
||
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| Advert | |
| 
         | 
    
| 
			
			 | 
		#6 | |
| 
			
			
			
			 Junior Member 
			
			![]() Posts: 8 
				Karma: 10 
				Join Date: Mar 2021 
				
				
				
				Device: Kindle PW3 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			UPDATE: 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Finally found the solution for this! In order to change the z-index for the forward and backward zones, the order in Code: 
	overrides = {},
Quote: 
	
  | 
|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#7 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Passersby: don't actually empty the table. Keyword being "reorder", not "empty". 
		
	
		
		
		
		
		
		
		
		
		
		
		
			The gnarly details involve building a depgraph from these lists, and insertion order is preserved. TL;DR: A simpler tweak would just be to re-order the original registration of the tap_* zones, which is what I linked in my original answer. Last edited by NiLuJe; 04-18-2021 at 03:48 PM.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
![]()  | 
            
        
    
| Thread Tools | Search this Thread | 
            
  | 
    
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| Fbreader ios vs android tap zones | peaceridge | Reading and Management | 4 | 11-29-2020 01:43 PM | 
| Two separate 'tap forward' zones? | Pavati | KOReader | 10 | 07-19-2020 07:55 AM | 
| Custom tap page turn zones | ReaLx3m | Kobo Reader | 8 | 10-20-2017 08:41 AM | 
| Changing Tap Zones | MSch | Kindle Developer's Corner | 6 | 03-03-2013 06:14 PM | 
| Time Zones | Tinks | Feedback | 9 | 01-01-2011 09:31 PM |