Thread: Plugin devs: Upcoming migration to Qt 6
View Single Post
Old 01-04-2022, 10:57 PM   #55
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 jackie_w View Post
Well, if you've never needed them I'm not sure why I'd need them either.

Unless someone comes up with a good reason not to I think, from now on, I'll just go with the simple option, i.e
Code:
QTableWidgetItem.__init__(self, text)
The Qt docs say:

Quote:
You can define new user types in QTableWidgetItem subclasses to ensure that custom items are treated specially.
It's probably for plases where you can get a QTableWidgetItem subclass without knowing what it is. And you can use the type to cast or otherwise handle it appropriately. But, I can't find an example that does anything other than set the value.

Looking at the examples I have, that isn't going to happen. Most set flags and the data and don't do anything else.
davidfor is offline   Reply With Quote