View Single Post
Old 04-08-2020, 06:08 PM   #4
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
Originally Posted by theducks View Post
2 issues with this PI

1) The column name required is #lastopened

2) This PI pops an error every time you use Calibre on a Library that does not have (or want done) tracking Only Affects those with multiple libraries
A per Library configuration would be handy. This could also contain the fieldname to use. no name- no gripe First per Library use adds Library name entry and waits for user input for field (option to create: w/restart requires)
There is a new Job Spy GUI Tool to replace this plugin that is compatible with a multiple-Library ecosystem. It turns itself on or off after Quick-Switching depending on the Libraries stated in Customizing, and whether or not the user-specified custom column exists in the appropriate Library, and whether or not the custom column is a 'datetime' type or not.

It also assumes that every user wants their very own special custom column name to use. Nothing is hardcoded.

Python 3 compatible, of course.

I will release the new Job Spy version after I finish testing the new tool.




DaltonST
DaltonST is offline   Reply With Quote