View Single Post
Old 09-05-2014, 08:35 PM   #22
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 DaltonST View Post
Apparently Calibre 2.2.0 broke: from calibre.gui2.dialogs.message_box_ui import Ui_Dialog .

Going from Qt4 to Qt5 there was plenty of warning. If truly Calibre 2.2.0 intended to remove message_box_ui, then it is a lick on Calibre to do so with no prior notice.

Any plugin that uses from calibre.gui2.dialogs.message_box_ui import Ui_Dialog will fail.
And that is actually the plugins fault. You should not be using this directly. It is code generated from message_box.ui during build. Or, if you are running from source, it will be generated during startup.

You should change your code to use:

calibre.gui2.dialogs.message_box import MessageBox

Or write your own message box if it isn't suitable. But, look through the definitions in calibre.gui2.__init__. There are a lot of different message boxes in it you could use.
davidfor is offline