Model/View Performance

[Stevildo]

Thank you wysota for your reply!
If I started with this project I read a lot about MVC and the Qt models. I thought that it would be very complex to implement my own model based on QAbtractItemModel.
And I wasn't sure if this will be really necessary. So for the first step I decided to use QStandardItemModel and expand it with my needed functionality. And everything works fine except the above written performance problem.
Do you think I can fix the problem by deriving from QAbstractItemModel?
Is there a good tutorial on how to do this? (I've found a link to a tutorial on this forum but I get an 404 Error...: http://doc.qt.io/qt-5/itemviews-simpletreemodel.html)
On which point do I have to ensure that I will not run to same trouble as I get with QStandardItemModel?
Is it only a problem of the model or also the view?
Is there no other QStandardItemModel based solution?

Thank you for your help!!

[wysota]

Do you think I can fix the problem by deriving from QAbstractItemModel?

I cannot guarantee that but there is a good chance you will get decent performance boost if you implement the model properly.

Is there a good tutorial on how to do this? (I've found a link to a tutorial on this forum but I get an 404 Error...: http://doc.qt.io/qt-5/itemviews-simpletreemodel.html)

Following a tutorial will not do you much good. A good model has to be tailored to the data it holds. If you follow a tutorial your model will be suited for data presented in the tutorial. You have to first understand what you are doing.

Is it only a problem of the model or also the view?

You rarely have to touch the view. I'd focus on the model.

Is there no other QStandardItemModel based solution?

Without knowing the details of the behaviour of your data I cannot answer that question. Item based models are usually much slower compared to models which directly operate on real data structures and signal changes to the model in a smart way.