Quote:
Originally Posted by DVdm
Yes, I already use that.
But I have just now solved it by explicitly tweaking the sort at startup setting from
sort_columns_at_startup = None
to
sort_columns_at_startup = [['#read', 1], ['authors', 0], ['series', 0], ['title', 0]]
This used to be not necessary. Now it seems to be...
|
none is equivalent to the
naturalsort order of the DB (I believe {id})
Anything done that affects the overall Library (like a repair-rebuild) can result in a new ID. Date remains as the dater the entry was made initially (unless tampered with)
Read
as a sort make little sense with the preceding sort. (#read can be a
FILTER)
As a matter, your whole sort is odd. SORT is about arranging mutually Exclusive values, with levels, breaking ties.
Series has series_index to refine the order (title)
You can't sort by Title And Index. They usually are exclusive (Unless it was the Alphabet Murders. A was 1, Y was 25)
And using Authors as an Overall, also fails if your Library has shared universe type series.