Still not sure what's the best design here.

What's the benefit of FileSystemModel::getFileInfo()? I would guess your this pointer is a nullptr

@sierdzio said in How does MQL TreeView release its resource?:

I have a workaround: store the data and delete it at the next refresh event.

In order to have more control, my final choice is to delete it manually instead of using auto pointer.
But anyways, thanks for your suggestion.
Kevin

@JKSH Yep I'm having a full run through the app now to ensure everything happens in GUI thread - that is widget/affects widget.

@Dariusz said in QAbstractItemModel asserts & multithreading:

Hmmm I think this might not work for me

Why not? It makes no difference if you push or pull the data... but it's up to you :)

You are trying to overload the Data function by data(parent) but the real signature of this function is data(index,role)

Try to replace for this sneap of code:

def data(self, index, role, *args, **kwargs): if role == Qt.DisplayRole: return "hi" return None

You also need to import Qt from QtCore module.

#from PyQt5.QtCore import QAbstractItemModel, QModelIndex from PySide2.QtCore import QAbstractItemModel, QModelIndex, Qt

@Joachim-W Then please mark this topic as solved, thx.

@SGaist Awesome thanks! I think I can get it to do my bad biding now :- )

You may also try to set dynamicSortFilter: true, but only if you do not modify contents of model through proxy model.
invalidate() calls are expensive and you should only do it when you know what you are doing.
If you modify contents of your model through proxy model and/or you need to filter and sort on demand, invalidateFilter() and sort() is what you are looking for.

@raven-worx said in QTreeView/Model drop action - no expand sign ?:

Also did you emit the dataChanged() signal on the parent index?

I've just read the post. I forgot to correct it. This is what I edit:

bool testModel::dropMimeData(const QMimeData *data, Qt::DropAction action, int row, int column, const QModelIndex &parent) { ... Q_EMIT dataChanged(itemFirst.index(),itemLast.index()) }

Hmmmm so I tried this, the parent is the object that is in function above.

Q_EMIT dataChanged(parent, parent)

Now this now "magically" works, I get extra ">" when I drop item on another item...
I also learned that I also need to call Q_EMIT layoutChanged({parent}/flag) to update view if I drop items on expanded parent...

Ok all good then, thanks! Weird issue o.o

@SGaist Woah... I have lots to read! Thanks! Gotta dig into proxier more then.

@Dariusz I'm a nob. I captured selection range after action and not before. Storing selection before calling QTreeView::mouseReleaseEvent(event); seems to have solved the issue.

Ok I found what was causing this awful bug.

When I check if the map contains the index, I actually check the raw index not the QPersistantModelIndex so this is not the same object and I think qmap does not check equality using == operator .

So I have to iterate over the map and check using QPersistantModelIndex "==" operators which can compare from a QModelIndex.

Hey

Just thoguh I'd drop a "temporary" solution I'm testing now. I ended up extending qtreeView, and capturing expand/collapse signals. Then I generate a QSet with these ids that later I can store/restore via model()->match(id) idea. Not sure how well it will work in very large data sets, say 100k items and 10k expanded state items, But well see.

@Dagginio
Hi
just call update() to have it refresh when "status" changes.

-Do I have to remove that blue frame before I paint a grey one?
depends if you have autofillbackground on widget on.
in that case it will be cleared default.
else u might have to. try without and see

Not a good idea indeed. Why would the item have to know anything about what stores it ?

rather than the delegate I'd reimplement QTreeView:
protected:

virtual void drawBranches(QPainter *painter, const QRect &rect, const QModelIndex &index) const virtual void drawRow(QPainter *painter, const QStyleOptionViewItem &option, const QModelIndex &index) const

and slots

void collapse(const QModelIndex &index) void expand(const QModelIndex &index)

But agree is not straightforward and will require some work

I tried to understand by reading your description. I should appreciate your patience to write this whole description.

Coming to you issue, you are using model and view with View has single column. You are using the repeater. It is single column there. This requests for index with row and column=0. This is how it works always. If you are using TableView with appropriate TableModel then it will request for row and column values.