TreeView not updating after a dataChanged signal

Coubz

@SGaist Yep I've tryed that already.
It shown me some issues that i've corrected but the datachanged(...) still doesn't do anything.
One noticeable fix was to return an invalid QModelIndex with the parent method when the parent is the root node of the tree.
Is there a way to be able to break in the TreeView code to follow the signal reception an see what's wrong?

Coubz

Is it possible that i miss something to set the TreeView as "dirty" ?
The TreeView or an other Qml element that contains it, or the items inside the view maybe.
It's weird because as i said if i drag the view to move the text of the items outside of the windows thay will update.

Currently the hierarchy is something like that :

ApplicationWindow
    Rectangle
        GridLayout
            Item
                ColumnLayout
                    Item
                        Rectangle
                            TreeView
                                TreeViewDelegate
                                    Row
                                        CheckBox
                                        Text

Christian Ehrlicher

Your dataChanged() is wrong somehow. Minimize your code, remove qml and use a simple QTreeView until you can either reproduce it in a minimal compilable example or find your bug. The models work correct and don't need a special update except dataChanged() when some data changes inside the model.

JonB

@Coubz
I agree with @Christian-Ehrlicher. I would suspect the dataChanged() signal itself is fine and being acted on, but somehow the indexes are not what you think they are so it does not redraw the right thing?

Coubz

I've managed to make it work, i'm not exactly sure to understand why tho.
I had to change the way the setData reacts :

bool MapMarkerTreeModel::setData(const QModelIndex& _index, const QVariant& _value, int _role/* = Qt::EditRole*/)
{
    if (!_index.isValid())
    {
        return false;
    }

    if(MapMarkerTreeItem* item = getItem(_index))
    {
        if(item->setData(_value, _role))
        {
            //emit dataChanged(_index, _index); // <-----  Previous version

            QList<int> roles{Qt::DisplayRole, Qt::EditRole, _role};
            QModelIndex id = createIndex(_index.row(), item->getColumnIdFromRole(_role), item);
            emit dataChanged(id, id, roles);
            return true;
        }
    }

    return false;
}

So it seems that the dataChanged signals have to build the role into the column of the ID else it won't refresh properly.
I thought the role param of the signal would be able to do the trick but i think there is something i didn't understood here.

JonB

@Coubz
You posted this topic in General and Desktop rather than https://forum.qt.io/category/12/qml-and-qt-quick. I assumed you were talking about a Qt widgets QTreeView. Are you in fact using QML and its TreeView? You never mentioned QML....

SGaist

@Coubz well, once you mention using QML it starts to make sense.

QML uses custom roles to access data hence if you don't tell dataChanged that the data corresponding to these roles has changed, then there's no reason for the view to update.

Coubz

Yes i do use QML sorry.
So what you're saying is that if you use QML the roles handled on the code side are irrelevant ?
It seems a bit weird as if a edit a values at runtime i do get the proper role in the setData callback.
It just that i've neglected the column of the index because i was thinking that the view won't be needing it as it had the role. And because the setData callback have an index without the column setup when trigged by edition.

SGaist

Quite the contrary, proper role handling is paramount to have a correctly working model view implementation.

Oleksii_S

Just want to share some debugging tips for the issue:
Step 1: Put the debug output inside data method of your implementation the QAbstractItemModel class, like

QVariant TestViewModel::data(const QModelIndex &index, int role) const
{
        qDebug() << "data" << index.row() << index.column() << role;
        ...
}

Then make sure you are updating the cell with same index adding the same output before emiting dataChanged signal.