View Single Post
Old 09-09-2016, 11:46 AM   #1
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 6,984
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Question calibredb set_custom(etc) GUI refresh?

I'm looking through the source for calibredb and noticed that while some commands (add/remove/add_format/etc) send an IPC message to the running GUI to refresh, other commands (set_custom/add_custom/etc) do not. And I can see the difference in the running GUI.

Is using calibredb while the GUI is running: allowed, not allowed, or only allowed for certain commands?

The only reference on the calibredb manual page is the --dont-notify-gui option which implies it is allowed.

The only other reference I've found says "don't do custom columns while GUI is running", but it is quite old.
JimmXinu is offline   Reply With Quote