On Friday, April 22, 2022 3:39:08 AM CEST Fusion Future wrote:
> One major difference I have found is that KConcatenateRowsProxyModel
> will check if sourceModel exists when mapping from/to sourceModel, but
> QConcatenateTablesProxyModel won't. So if QConcatenateTablesProxyModel
> doesn't receive `
The backtrace can be seen from https://bugs.kde.org/show_bug.cgi?id=445479
I would like to know the difference between
QConcatenateTablesProxyModel and KConcatenateRowsProxyModel, because
simply replacing KConcatenateRowsProxyModel with
QConcatenateTablesProxyModel seems problematic.
Thanks in advance.
One major difference I have found is that KConcatenateRowsProxyModel
will check if sourceModel exists when mapping from/to sourceModel, but
QConcatenateTablesProxyModel won't. So if QConcatenateTablesProxyModel
doesn't receive `rowsRemoved` signal from sourceModel,
QConcatenateTablesProxyModel
seen from https://bugs.kde.org/show_bug.cgi?id=445479
I would like to know the difference between
QConcatenateTablesProxyModel and KConcatenateRowsProxyModel, because
simply replacing KConcatenateRowsProxyModel with
QConcatenateTablesProxyModel seems problematic.
Thanks in advance.
