Quote:
Originally Posted by kovidgoyal
Sure, this would be worth doing in principle, except that it is a huge job, because machine generated and user generated data are not differentiated in any way in the calibre code base.
What I would really like to figure out is the how and why of this happening. Unfortunately, I have never been able to reproduce. It is not at all clear to me why layout/geometry preferences should be the only preferences to get "stuck" in a particular config file. The config file is basicallya JSON dictionary, so corruption should prevent the entire dictionary from loading, not just cause a single setting to get stuck.
|
Maybe as a workaround/diagnostic - a 'feature' that :
- asks which component - library manager, editor, or viewer
- logs the layout/geometry values as they exist
- removes, them from the json file
Assumes component will regenerate missing values in the json file and leave the rest as is - which I suspect they already do.
User would post log here, in a sticky thread - maybe a pattern will emerge, albeit over a long period.
BR