Thread: Instructions for patching firmware 3.15.0
View Single Post
Old 05-10-2015, 09:07 PM   #77
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Siard View Post
Further investigations reveal that, after switching on the device, the database is not read until something is altered in the DB, e.g. by moving some slider.
Without the line height patch, the line height is taken from the global configuration file. With one of the two patches applied, it is probably also taken from there, but the line height becomes a certain smaller proportion of that, say 75%.
After moving some slider, or connecting with USB and disconnecting, the values are taken from the database.

Until firmware version 2.8.1, a line height of 1.35 was common. But from 2.10 on, line heights were displayed much wider, so 0.88 became optimal. But 1.0 remained the minimum value that could be set with the slider, so that's why the patch became wanted.


These fields contain the correct line height values, 0.88 in my case.
But, as explained, these are only read after something in the database has been altered.
Which makes no sense. How does the device render the page using the settings for the book if it doesn't read the database? That is the point of the content_settings table; per book reading settings. When you make a change to the settings while reading a book, they are stored in the database and the config file. When you reopen that book, the settings used are from the database, not the config file. And, unless it has changed recently, the value used doesn't have to be one reachable on the slider.

The problem is probably in how the settings are matched against the values for the slider. If the value in the database, or config file for that matter, doesn't exactly match a choice on the slider, then it chooses a setting that is on the slider. From memory, it is one of the settings either side of the value, but I haven't played with that recently. Does your 0.88 setting match something that you put into the patch for the line heights?
davidfor is offline   Reply With Quote