Quote:
Originally Posted by BetterRed
@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
|
So I've tried the new library and such and see that works. I discovered a new problem while testing this about logic custom columns not copying (separate thread), but I've also learned more about .json files.
I do see that my problem library's metadata_db_prefs_backup file last updated in April! It is not updating when I make changes or close my library.
So......
Is that file one that can be DELETED, then allowed to restore? Does it store EVERYTHING that I don't want to lose. I've considered copying it to make a backup of the not-updating "backup" then deleting it to see what happens. Then, I think I could replace it with that messed up one if needed.
I fear trying that without someone who's in the know saying it's not a problem.
Obviously I've been adding new columns and settings since then that are not in the backup. They are still there when I go back.
I have another library that has the same setup, but it DOES update. Could I copy that metadata_db_prefs_backup file to this one if it's just about saving the views and/or configuration. I would assume based on what's happening that new columns in the problem database would not be affected. I'd just have to turn on their view since they aren't in the other library.
Any more input you cold offer???