Quote:
Originally Posted by Markismus
This is wrong.
Koreader does no detecting whatsoever to a "nightmode plugin".
Koreader's normal generation of the screen data (frambuffer) includes an inversion of the whole screen from LCD to eINK (invert blitbuffer). (This was explained to me on github as that the higher value for the color on a LCD makes it brighter, whilst it makes it darker on an eINK screen.) Turning on nightmode means that this inversion doesn't need to take place. (So nightmode uses less processing time.)
Nightmode in koreader is not a hack in the system to invert the framebuffer send to the screen, but elegantly generates the framebuffer differently and less processor time consuming.
|
Sorry, my mistake. I mixed the koreader nightmode with KSM that work like I explained before because I always use koreader from KSM.
Again, sorry for my confusion