Quote:
Originally Posted by BetterRed
Why not separate the layout data from all the user supplied data. I can recall other instances of similar layout issues as this one. Happened to me once with the viewer, it got stuck on full screen.
BR
|
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.