View Single Post
Old 12-12-2020, 11:01 PM   #5
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
So if a GUI plugin exrcutes a db.add_book() many times quickly, how does it now (5.7) notify Calibre to update the Cache from the physical DB so that the library_view can be subsequently updated from the refreshed Cache? That is the very real problem. 5.6 could do that. 5.7 now requires a Calibre restart to show the new books, which is unacceptable.

I tried using the "bookedit:" message in a loop for each new book_id, but the Listener refuses the connection because it sources from an unknown server.

Is a GUI plugin now considered a different program?
DaltonST is offline   Reply With Quote