View Single Post
Old 08-28-2014, 02:26 AM   #6
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
Quote:
Originally Posted by kovidgoyal View Post
Just uninstall the doc input plugin and wait for it to be made compatible with calibre 2.0
I just saw the checkin to fix the way the DOC Input plugin loads the configuration widget. This had me baffled for a while as it crashed calibre on my machine. It took me longer than I like to think to find the offending code.

When I looked, some code was added to gui2/convert/__init__.py on 30/06/2014 that broke what was in the plugin. The strange thing is that the change was checked in by the author of the plugin but the plugin was never updated to match. When I removed the code from the plugin, everything worked perfectly.

I have the plugin ready to go. It works with both 1.48 and 2.0. And your new code. I just want confirmation from another person who actually uses it before it gets released.
davidfor is offline   Reply With Quote