View Single Post
Old 01-08-2021, 09:21 AM   #9
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,203
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Thanks, Kovid. Will do it that way.
  • What is the earliest calibre version that supports this?
  • Is there any use for the older interface? the one you get from gui.current_db, or should I always use the new_api? I want to replace all db references with the new_api if possible. If not possible I will have to use a naming convention to differentiate them to avoid confusion.
  • when calibre passes references to db — e.g. library_changed(self, db) — which one does it reference?
capink is offline   Reply With Quote