View Single Post
Old 10-04-2016, 09:36 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
No, the count pages plugin is directly updating the books metadata with data it calculates or downloads. Then it triggers an update to the interface to get the list refreshed.

calibre/src/calibre/gui2/actions/edit_metadata.py isn't exactly what you want, but it does have the clues. "edit_metadata" appears to be what happens when you press the toolbar button. This collects the list of selected books and calls "edit_metadata_for". That then calls "do_edit_metadata" with the list. And that calls "edit_metadata" from "calibre.gui2.metadata.single". And that appears to be what opens the actual metadata editor.

Looking at that, the problem is going to be making sure you pass the correct objects through to the editor.
davidfor is offline   Reply With Quote