Originally Posted by davidfor
So, each time you set it to a particular size you don't want the tirgger changes the value to the unavailable size you do want?
Yes. My SQL is rather rusty and I wasn't able to get it to work by attaching the trigger to the font settings table (content_settings), so I added it to the Bookmark table instead, hence the 'kludge' description.
After the trigger is added (simple one-time hack), the process for any book is
- set the various font settings sliders to 'unwanted unusable' values (e.g. min. font-size, max. line space).
- create new bookmark to force trigger to fire, (changes 'unwanted' values to 'wanted' values in content_settings)
- exit book/re-enter book (new font values will be read)
- delete bookmark (or not)
I have considered creating a new thread to discuss the wisdom of doing this and give a detailed step-by-step if required, but I'm unsure how 'safe' this hack is if Kobo do an automatic upgrade to the database whilst the trigger is in-situ. I'm happy to take the risk for myself but I don't know whether advocating the addition of an SQL trigger would be considered as 'irresponsible' hacking.
I've been using this for the last couple of weeks with no apparent problems. The Kobo font settings feature is no more/no less flaky than it's always been (i.e. quite flaky).
And thanks for the explanation about the Sonys.