How to insert many items into QListView without making the app freeze?
-
The problem is, that QStandardItemModel does not support the idea of a transaction: an operation in which you put in a lot of data at the same time, and you want to make that atomically. That's why I wrote my own item model in the past for cases where I did not want to create a QAbstractItemModel that operates on my store directly. That model supported such transactions by simply caching the list of modified, added and removed items, and sending the signals that contained the whole set of changes in one go. I think you will need something like that too.
Here's what I did (GPL code):
http://www.assembla.com/code/srtools/git/nodes/unstable-db/common/src/storingtablemodel.h
http://www.assembla.com/code/srtools/git/nodes/unstable-db/common/src/storingtablemodel.cpp -
No, it is part of a much bigger project. I just refered to it as an example on how you could do this, not as a piece of ready to use code that you can just use in your project. This particular implementation depends on a matrix class that I wrote for that project as well, but that is just a class that makes a 2-d array looks nice.
-
I keep them in a memory structure, yes. So does QStandardItemModel. You can use any convenient memory structure. I already had a flexible matrix class in that project, so I decided to use it, but you can find plenty of alternatives. My version worked with QVariants to stay close to the QAIM API. If you want to use other types, you should considder if you should not rather create a real 'store' kind of object (-hierarchy) that provides a good, well structured API to access your data objects, and create a QAIM that works as an interface between that store and your item views.
-
-Another approach would be to subclass [[Doc:QAbstractListModel]] (you're using the model an a list view, right?) and reimplement the relevant methods. I'm with Andre here, what you need is not achievable with the QStandardItemModel with reasonable effort.-
I take that back. Looking at the snippet, I overlooked the setIndexWidget() call at first sight. One cannot speed up this much.
-
Thanks you both for the help . to understand it more .
@Volker what do you mean by :
"need is not achievable with the QStandardItemModel with reasonable effort."
what is wrong with the QStandardItemModel im using ?
what is not achievable with QStandardItemModel that i will need to implement with QAbstractListModel? the adding the items into memory ?
Thanks again . -
With a subclass of the QAbstractXXXModels you can connect the webservice to the model directly. In that processing method you tell the model that you are going to change its contents, then you do the actual changes, then you tell the model that you're ready. This cannot be done from outside the model, as you would have to do with the QStandardXXXModels.
But I read back and noticed, that you use setIndexWidget(). This isn't handled by the models at all, but only by the view. So you cannot speed up things by using another model class here.
-
Ah, I missed the use of that method as well. Sorry.
All bets are off. It is a wart on the face of the model view framework, and it makes sure the whole thing is basically useless. Putting more and more widgets on your view is never, ever going to be fast. Sorry. -
Andre , i asked this and other forums before but i could find solutions to
things like making label with mouse select text for copy when i tried to use
itemdelegate"developer.qt.nokia.com/forums/viewthread/13515/":developer.qt.nokia.com/forums/viewthread/13515/