Quote:
Originally Posted by ownedbycats
I switched my #onreadinglist composite column to instead check for the presence of "To Be Read" in the #kobocoll column; that didn't help.
But what did help was removing Reading List entirely from the View Manager sort order.
|
Quote:
Originally Posted by ownedbycats
Creating a new column didn't work. Unfortunate.
|
There are potential API ordering problems when changing columns. AFAIK one should a) change all the columns, then b) do a reset_ids() on books that might have changed. Doing a set_field() does not notify the GUI that something might have changed.
I can think of two problems that can arise. 1) If a column is changed after the GUI is notified or without notifying the GUI then the search and sort caches can have incorrect values. 2) If a field changed without a reset of the book then the composite columns for that book might not be recalculated (another book cache issue).
I know nothing about how Reading List does its job. Does it notify the GUI using model.reset() or model.reset_ids() after changing anything? Does it do a cache.clear_caches()?