In 90% of the cases you can use QStandardItemModel instead of going through the minefield that is subclassing an abstract model.

My advice is just to use that "universal model" instead of a custom one. If you really, really want to customise it as performance of QStandardItemModel is a problem then make sure you run your model through the Model Test (needs just a couple of trivial fixes to work on Qt5) that will tell you if you did everything as you were supposed to or you fell in the countless pitfalls of model subclassing

@Swapnil_Shelke

Happy to see that it helped you,

You are welcome =)

@skebanga Many thx!

Hi,

You can try implementing a QStyledDelegateItem and paint only the icon.

Hope it helps

The QTableWidget is item-based. meaning you insert the data into the widget and it takes control of it. (owns it)
So sharing between QTableWidgets is not really working.

However, the QTableView is a view-model object.
Here your data lives in a object (the model) that the QTableView asks for data.

It is possible to share this model between QTableViews and if you
update any field, it would be the same for all as "playername" would only exists once.

So if you have not,please read about QTableView and Qt's model/view framework.

If only player name is shared, then using a model might be a bit overkill. Still super flexible.