MobileRead Forums - View Single Post

NiLuJe · 01-06-2020, 02:17 PM

Okay, #311 updated

.

There's a new setting, "aggressive_timing", which, when set to 1, will toggle the behavior mentioned earlier, which should help getting the clock updated much closer to the page turn when reading KePubs.

As explained earlier and in the config, this is disabled by default, because the ePub reader is terrible (i.e., there's no behavior change with the default settings).

The list of things that "break" this more aggressive behavior is non-exhaustive, so, if you try it, and find something else that "breaks" but worked with the defaults, do mention it, so I can at least document it

.

I also fixed a related issue that prevented the "delay" setting from actually handling decimal values (and, worse, took down MiniClock with it if you tried), and amended the comments around it to explain how it interacts with "aggressive_timing"

.

TL;DR:

I did the testing on a H2O with:

Code:

aggressive_timing=1
delay=0.25 0.5 1

01-06-2020, 02:17 PM	#374
NiLuJe 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	Okay, #311 updated . There's a new setting, "aggressive_timing", which, when set to 1, will toggle the behavior mentioned earlier, which should help getting the clock updated much closer to the page turn when reading KePubs. As explained earlier and in the config, this is disabled by default, because the ePub reader is terrible (i.e., there's no behavior change with the default settings). The list of things that "break" this more aggressive behavior is non-exhaustive, so, if you try it, and find something else that "breaks" but worked with the defaults, do mention it, so I can at least document it . I also fixed a related issue that prevented the "delay" setting from actually handling decimal values (and, worse, took down MiniClock with it if you tried), and amended the comments around it to explain how it interacts with "aggressive_timing" . TL;DR: I did the testing on a H2O with: Code: aggressive_timing=1 delay=0.25 0.5 1 Last edited by NiLuJe; 01-06-2020 at 02:21 PM.