Frans de Jonge
Frans de Jonge
Note that it has seen some minor tweaks since the last release.
> But why it adresses Kobo light then? Maybe it was used as the basis? There has been at least some refactoring of the brightness/warmth stuff since but at one...
Yeah, it sounds like a really weird idea. It should work more or less the reverse of regular LCD/OLED behavior but even then that's a weird and unnecessary delay.
> Instead of koreader looking through all of them anyway because, I assume, it makes lookups very slow, what's the point of disabling them? Exactly that. Also even in circumstances...
For reference, on my Kobo Aura H2O it takes about a second with 6 reasonably sized dictionaries enabled.
Is that with the Kindle legacy build?
I'm not sure if I agree that it isn't appropriate, but I do agree that I don't particularly want to maintain it if Kobo changes their API or something. >...
I hadn't noticed that, or rather I hadn't looked at the code but I was merely talking about the concept as described in the OP. I assumed it was only...
The sleep cover there is just a red herring. The log is [the same](https://github.com/koreader/koreader/issues/12787#issuecomment-2514953144): ``` 12/03/24-09:43:09 INFO Kobo suspend: going to sleep . . . Cannot write `mem` to file...
That's what I just said a few hours ago. ;-) https://github.com/koreader/koreader/issues/12787#issuecomment-3195840018