[Solved]QSortFilterProxyModel Crashes

[A Former User]

@SGaist
Found a work around.
Clear proxy model first, then set source model again.

    _proxyModel->clear();
    _proxyModel->setIsMaxMinShown(!_proxyModel->isMaxMinShown());
    _proxyModel->setSourceModel(_vm);
    emit _vm->layoutChanged(); // change this to emit from vm class.

[A Former User]

@sharethl
Clear and set source model again still have chances to crash.....

[A Former User]

@sharethl
Remove this line working
emit _vm->layoutChanged(); // change this to emit from vm class.

[karlheinzreichel]

to update your table, you better use
emit dataChanged(modelIndexFrom, modelIndexTo);

[SGaist]

Are you sure _vm is not null ? And again, don't call emit on other classes like that, it feels like your doing some bad design.

[karlheinzreichel]

You have to emit layoutAboutToBeChanged() before you change your model
and emit layoutChanged after your model changes to reflect the changes to the ui
(see documentation void QAbstractItemModel::layoutChanged())

some code

void MainWindow::on_pushButton_clicked()
{
   _vm->tellLayoutAboutToBeChanged();
    _proxyModel->setIsMaxMinShown(!_proxyModel->isMaxMinShown());
    _vm->tellLayoutChanged();
}

void Vm::tellLayoutChanged()
{
   emit layoutChanged();
}

void Vm::tellLayoutAboutToBeChanged()
{
   emit layoutAboutToBeChanged();
}

[SGaist]

That design is completely wrong. It's the responsibility of the model to know when to emit anything. The proxy will make the signals follow. It's not the role of MainWindow at all to call these functions.

[A Former User]

@SGaist Yes, bad design, will correct this.

[karlheinzreichel]

@SGaist
You are absolutely right.
But the question was for the reason the application crashes.

The reason for the crash is not the architecture but the missing layoutAboutToBeChanged()

[SGaist]

Still, that call is not done at the right place, so you're currently just lucky it works.