Thread: [GUI Plugin] Count Pages
View Single Post
Old 07-31-2022, 10:32 AM   #1551
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 astergremlin View Post
calibre, version 6.1.0
ERROR: Unhandled exception: <b>AttributeError</b>:'QTextEdit' object has no attribute 'setTabStopWidth'

calibre 6.1 embedded-python: True
Windows-10-10.0.19044-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19044')
Python 3.10.1
Windows: ('10', '10.0.19044', 'SP0', 'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeDRM (7, 1, 0) && Count Pages (1, 11, 2) && FanFicFare (4, 14, 3) && Obok DeDRM (7, 1, 0)
Traceback (most recent call last):
File "calibre_plugins.count_pages.config", line 322, in view_prefs
File "calibre_plugins.count_pages.common_utils", line 817, in __init__
File "calibre_plugins.count_pages.common_utils", line 838, in _init_controls
AttributeError: 'QTextEdit' object has no attribute 'setTabStopWidth'
I'm getting this QT6 error in the latest update. I found a couple of other threads on the forum that seem to address this specific issue. Just a heads up so it can be fixed in the next release

Here's a link to a potential fix https://www.mobileread.com/forums/sh...&postcount=104
My apologies for not replying earlier. I know of this and have deliberately not fixed it yet. That function is only intended for debugging and should rarely be used. And is in a lot of plugins. I have been waiting for things to settle down before fixing this in case there is an issue to fix elsewhere. I will try and update it sometime in the next week or so, but, it will be a low priority.

Were you needing to do something with this dialog? Or just poking around?
davidfor is offline   Reply With Quote