From 25909f41a18f21f4aa9694e2e9eeded676135b16 Mon Sep 17 00:00:00 2001
From: John Factotum <50942278+johnfactotum@users.noreply.github.com>
Date: Thu, 9 Mar 2023 09:14:46 +0000
Subject: [PATCH] Make locations 10x bigger

Supposedly Kindle uses 150 bytes. Source:

https://www.mobileread.com/forums/showpost.php?s=6fbd6367bde3031320a271b6e3208445&p=1858934&postcount=3

However, since the way locations are calculated here is not exact
anyway, it seems more useful to use a smaller number that's more in line
with (1) the size of an actual page and (2) Foliate's old location size.
---
 view.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/view.js b/view.js
index acefedb..b410c6c 100644
--- a/view.js
+++ b/view.js
@@ -123,7 +123,7 @@ export class View {
 
         if (book.splitTOCHref && book.getTOCFragment) {
             const ids = book.sections.map(s => s.id)
-            this.#sectionProgress = new SectionProgress(book.sections, 150, 1600)
+            this.#sectionProgress = new SectionProgress(book.sections, 1500, 1600)
             const splitHref = book.splitTOCHref.bind(book)
             const getFragment = book.getTOCFragment.bind(book)
             this.#tocProgress = new TOCProgress({