View Single Post
Old 10-22-2020, 02:57 PM   #9
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 10,750
Karma: 74203799
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Quote:
Originally Posted by chaley View Post
No. Color and icon rules cache the compiled template, as does a composite column, so there is no difference in execution time. Calibre also caches the results of rule evaluation, so a rule is reevaluated only if calibre thinks the data might have changed. This is roughly the same as the process used to cache composite column evaluation results.
Is that part of the reason why an icon based on a composite template doesn't always immediately update when a column is modified by a plugin instead of the user?

For example: A #lastread date column, which is used for a composite psuedobool #currentlyreading. (It also checks the #read bool for a 'false' value.)

Column icons are set to display an icon if #currentlyreading returns a "true."

If the user manually edits the #lastread date, the icon appears immediately.

If the Job Spy plugin autopopulates the #lastread, the icon doesn't appear until the list is resorted (or occasionally until a new search is done, not sure why).

Last edited by ownedbycats; 10-22-2020 at 03:58 PM.
ownedbycats is offline   Reply With Quote