For me, the series info is populated, and either use a shelf or search on the series name. Then I sort them in my brain while looking for which one to read. And Recent sorting probably works best for me. I am looking for the first unread in the series and there is a good chance that will be the first one put on the device and hence at the end of the Recent sort. There is a big problem with that, but I don't have many series that are long enough to use more than one page in the search.
But something I have considered is fiddling with the SyncTime and setting it to the published date. For most series, that would give a rough series order. The other date I have considered is the date added to my calibre library. Part of the reason for both of these is that when you add a lot of books in one go, or do a sign-out, the books are added in alphabetical order by title. The order might be file name, but these are close enough matches for my books that it isn't immediately obvious. Either of these sorts would be more useful than the what the device does by default.
Quote:
Originally Posted by Stevex
(Did anyone ever play with this table to reshape the startup screen? I can see that would work)
While in operation, i think the kobo works off a memory copy of the database?
|
Apart from the current book tile (most recent book opened) and the sync tile (fixed in place, but removable via the database), the order of the other tiles is the reverse order for added to the database table. You can adjust what is on the page by adding or deleting rows or changing the value of "Enabled". Changing the order is a bit harder as you need to remove the current row and add it again. Or do whatever is needed to get SQLite to move the row.
If you are a calibre user, my Kobo Utilities plugin has function to dismiss tiles and add a trigger to the database to prevent their display. This doesn't work as well with recent firmware. I think the way they do the updates has changed. In the past it appeared to be "update the database then get the home screen to refresh". Now it seems they tell the home screen to display a tile and then update the database. This might just be because it is working on memory structures that only occasionally get updated from the database, but it means ttha the database trigger doesn't always prevent tiles from displaying.