<![CDATA[How to decouple a QStandardItemMode from a QTableView?]]>Hi,

How to decouple a QStandardItemMode from a QTableView? I tried it as below:

myTableView->setModel(myModel);
...
myTableView->setModel(NULL);  //decoupled here
...
myTableView->setModel(myModel);  //reset model after some work is done.

It caused a strange phenomenon: After reset the model, the signal QStandardItemModel::itemchanged is always triggered twice when I edit the model data. I'm confused... Anyone can give me a hint please? Many thanks.

]]>https://forum.qt.io/topic/139445/how-to-decouple-a-qstandarditemmode-from-a-qtableviewRSS for NodeMon, 09 Nov 2026 11:02:48 GMTTue, 20 Sep 2022 09:04:43 GMT60<![CDATA[Reply to How to decouple a QStandardItemMode from a QTableView? on Tue, 20 Sep 2022 09:33:42 GMT]]>@Lee908
setModel(nullptr) should indeed remove the QTableView from having slots attached to the QStandardItemModel, and setModel(myModel) again should set it to receive signals anew, without "doubling". However, "the signal QStandardItemModel::itemchanged is always triggered twice": attaching a view to a model connects its slots to model signals, it should not have anything to do with how many times any signals are triggered, which is a model-only thing.

Can you reproduce this behaviour in a small, standalone sample?

]]>https://forum.qt.io/post/729446https://forum.qt.io/post/729446Tue, 20 Sep 2022 09:33:42 GMT