Thread: Unwanted sort by date
View Single Post
Old 05-31-2023, 06:26 PM   #7
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,808
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by DVdm View Post
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...
I 'dodge the bullet' by using the optional View Manager (VM) plugin.

A few years ago, following some changes to VM, the built-in Date/timestamp(date) column injected itself into it's sort process - uninvited. The PI developer who made the changes offered an unconvincing explanation why it was so. As a consequence I didn't upgrade VM for a while.

I did tests every few months in calibre portable and after a couple of years it was fixed, I don't know if that was due to further changes to VM or changes in the calibre core.

BR
BetterRed is online now   Reply With Quote