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.
-
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.
@Lee908
setModel(nullptr)should indeed remove theQTableViewfrom having slots attached to theQStandardItemModel, andsetModel(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?
