Quote:
Originally Posted by ownedbycats
Created a fresh test library for replication and was able to repeat results even in a portable Calibre with only Reading List and View Manager. So here it is.
|
This is your idea of a "fresh" library?
There's 40+ columns, dozens of saved searches and your view sorts on 7 columns. And you haven't mentioned what column(s) aren't sorting correctly--just that a book is 'stuck at the bottom'.
Okay, I've followed your steps. Yes, the list-deleted book goes to the bottom of the list and stays there.
I changed the book's metadata, including setting and clearing the Reading List column to make sure that Calibre and not RL had touched it last. I manually clicked each of the sorts in order (except On Device but including hidden columns Currently reading and On Reading List).
The list-deleted book stayed at the bottom.
As far as I know, that's where it's supposed to be--I'm not taking the time to manually verify 7 sort columns for 14 books--but I will continue anyway.
When I quit and restart Calibre and run 'On Device' view, the list-deleted book is
not at the bottom immediately after restart, nor after running 'Default' view and then 'On Device' view again.
However, when I use Calibre's Edit metadata to add a value to the On Reading List column, save it, then remove it and invoke 'On Device' view, the list-deleted book is back at the bottom.
IMO, this absolves the RL plugin. But not necessarily VM.
Next test: I outright removed the VM and RL plugins, restarted Calibre, manually set and then cleared the Reading List column on the same book as before; then manually apply the sort order. The changed book is now at the bottom.
FYI, the default Calibre value for maximum_resort_levels is 5 (which is what I'm testing with).
I don't know whether it's changed or not, but in past, Calibre used to limit sort level to
4 on restart.
From an old VM post.
And that Calibre would force Date into the sort at least priority anytime it wasn't already included.
VM, as I understand it from the follow on posts,
does apply sort depth >5 when configured with more.
TL;DR: I submit that if there's a problem here, it's either in Calibre itself or ownedbycats' expectations.