View Single Post
Old 10-14-2015, 03:34 AM   #2
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,749
Karma: 30237526
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@jecilop - column position, alignment, show/hide etc working fine here on calibre 2.40, Windows 10 64 bit.

Book List relative column positions, alignments, widths etc are kept in the database not the configuration data. They can be seen in the metadata_db_prefs_backup.json file in the library, look for "library_view books view state" - best viewed with 'format aware' text editor like Notepad++, TextPad, Text Wrangler etc.

I suggest you create a small test library and see what happens with it. Monitor the changes in metadata_db_prefs_backup.json. I can't recall if that file changes dynamically or when calibre closes.

If you forget to pause cloud syncing before starting calibre, even just once, then that could result in database corruption, my understanding that calibre sources the book list layout data from the database. That .json is a backup for use by the calibedb --restore_database command

BR
BetterRed is offline   Reply With Quote