View Single Post
Old 01-15-2016, 07:17 AM   #80
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
@refj,
since your post is rather long, I will probably split my response up into serveral pieces.

Quote:
Originally Posted by refj View Post
They're in unified diff format so you should be able to apply my patches with `patch` under UNIX-like systems. Under Windows there must be some tool, but I can't help you there.
The problem I was having was that "patch" stopped with some error messages. I thought the reason might be that I tried to patch against the lua files of the last nightly build (koreader-nightly-20151213) and the patches concern newer versions. This is why I was asking for the already patched files. But since it was late at night, I maybe did some other mistake. But it does not matter so much now.

Quote:
Originally Posted by refj View Post
* First of all, related to the above: It's trivial to make KSM write to Nickel's config. To me it's important to be able to switch my device on in the night and for that I need brightness=1. ...
Actually, I was reluctant to make changes to config files of other applications, apart from offering the user to make changes (e.g. tools > nickel_diverse > edit_nickel_conf.sh).

If I were to give up this reluctance, I would think of something like this:
The basic idea is to have a file "currentlightlevel.txt" with the currently set/wished light level that we can read before starting an application, and write to after this application has exited. So I would give up dontTamperwithFrontlight and would replace it by syncLightBetweenApps (currently KSM, Koreader, Nickel).


in start_koreader.sh
  • before launching koreader: read light level from "currentlightlevel.txt" and set KOBO_LIGHT_ON_START to this value in defaults.persistent.lua
  • after koreader has exited: read the value of frontlight_intensity from settings.reader.lua and write it to "currentlightlevel.txt" (so that ksmhome.sh or (if we are in a switch-between-readers-mode) start_nickel.sh can read the light level)

Similar for start_nickel.sh

How do you think about this? (This idea does however not consider your recent proposals for koreader)
Edit: One problem is that in the koreader configuration files there is possibly nothing like nickel's FrontLightState.

Quote:
Originally Posted by refj View Post
* It would be nice to have these two by default in `ksm_ini_options.txt`'s [general]:
Code:
ksmAutoselectoption=start_nickel_koreader_switch
ksmAutoselectoption=start_koreader_nickel_switch
I take a note for the next update.

Last edited by tshering; 01-15-2016 at 06:26 PM.
tshering is offline   Reply With Quote