Quote:
Originally Posted by kiwidude
I definitely wouldn’t recommend messing with copying over the entire json file, it will wreck all your other plugin settings. If you were extremely careful you could copy the relevant json section from one to the other but chances are high you screw up with the wrong number of braces or commas unless you are diligent. So you should definitely keep a backup copy you can rollback to if you were to attempt it.
It sounds a reasonable feature request for the plugin. I will put it on the rainy day list to investigate. There are a few wrinkles I’m not sure how I will deal with until I try it - custom columns in a view that don’t exist in the target db, a view already existing with that same name etc. It will need at least one new dialog to pick the library. So not a five minute change…
|
Perhaps and import/export feature like Calibre does for their look/feel settings, and if the column doesn't exist then it does what the plugin currently does when columns in views don't exist and just skipps over them rather than throwing an error - or some kind of indicator that the columns have been changed.
ALSO - would REALLY like the ability to save an updated version of the view instead of having to rename it. I open views, fiddle with them and want to save them, but I have to rename them and end up with two views - one is outdated and the other is a different name. Too many Default, Newest Default, etc. Instead of going in and deleting them. I have to do this everywhere in Calibre so I suspect it's not something that is overlooked but rather a necessary evil. Just "save" rather than "save as"