Details
-
Suggestion
-
Resolution: Won't Do
-
Not Evaluated
-
6.0
-
None
Description
I see a lot of users that are approaching QTableWidgetItem using it in the wrong way due to the fact that the constructor forces to have a QString.
See for example: https://forum.qt.io/topic/68256/void-qtablewidget-sortitems
https://forum.qt.io/topic/82825/show-integer-value-in-qtable-widget
I see no point in forcing a QString as it immediately gets passed to setData that uses QVariant
I realise this is a break in the interface so should wait for Qt6 but it should not break source compatibility so I see no downside in changing it to QVariant