Best Approach for minimal footprint QListView of many thumbnail images
-
Hi
I think you can get this using a custom model
Where you override ( as the keys ones)
bool canFetchMore(const QModelIndex &parent) const Q_DECL_OVERRIDE;
void fetchMore(const QModelIndex &parent) Q_DECL_OVERRIDE;http://doc.qt.io/qt-5/qtwidgets-itemviews-fetchmore-example.html
Note: The sample is based on QAbstractListModel. You might want QAbstractItemModel.
-
Hi,
One thing you can do is use a "rolling window" in your model that loads only the thumbnails from the visible items. You could also delay the loading of the thumbnails until e.g. the view stopped scrolling for a certain amount of time showing a place holder in between.
-
Hi! Another possibility would be using a custom delegate to render the items. The model would only know the names of the files and the delegates would create the thumbnails automatically once they are shown. Also, once the delegates get automatically destroyed, the thumbnails would get destroyed, too. I think this would result in minimal memory footprint, although the GUI might feel laggy. If the latter should prove to be unacceptable you could use one or more seperate threads for the computation of the thumbnails.
-
Hi
I think you can get this using a custom model
Where you override ( as the keys ones)
bool canFetchMore(const QModelIndex &parent) const Q_DECL_OVERRIDE;
void fetchMore(const QModelIndex &parent) Q_DECL_OVERRIDE;http://doc.qt.io/qt-5/qtwidgets-itemviews-fetchmore-example.html
Note: The sample is based on QAbstractListModel. You might want QAbstractItemModel.
-
Hi! Another possibility would be using a custom delegate to render the items. The model would only know the names of the files and the delegates would create the thumbnails automatically once they are shown. Also, once the delegates get automatically destroyed, the thumbnails would get destroyed, too. I think this would result in minimal memory footprint, although the GUI might feel laggy. If the latter should prove to be unacceptable you could use one or more seperate threads for the computation of the thumbnails.
-
@mrjj Thanks, I'm looking at that example now. Seems to be a bit more involved when QAbstractItemModel is involved vs QAbstractListModel but I should be able to figure something out.
@JMO_GS
Hi
The rolling window as @SGaist might be better than the FetchMore way, as fetch cannot unload again. ( as far as I know )
Or using delegate as @Wieland suggests.Not sure would be the easiest to get doing.
Also I kinda like your logic using QStandardItem::data() and Qt::DecorationRole but im not sure
when it would be called.If you need to "unload" over time, you should aim for solution that does this easy.
-
@JMO_GS
Hi
The rolling window as @SGaist might be better than the FetchMore way, as fetch cannot unload again. ( as far as I know )
Or using delegate as @Wieland suggests.Not sure would be the easiest to get doing.
Also I kinda like your logic using QStandardItem::data() and Qt::DecorationRole but im not sure
when it would be called.If you need to "unload" over time, you should aim for solution that does this easy.
@mrjj I'm not sure what you or @SGaist are talking about by a "rolling window". Obviously that describes the effect I am trying to accomplish: A rolling window... class that loads/unloads thumbnails as needed. But I'm sure if you literally mean some specific Qt class or not? Whatever I use to achieve this must somehow be tied into the existing QListView signals, yes? Like checking scrolling notifications or the like?
-
@mrjj I'm not sure what you or @SGaist are talking about by a "rolling window". Obviously that describes the effect I am trying to accomplish: A rolling window... class that loads/unloads thumbnails as needed. But I'm sure if you literally mean some specific Qt class or not? Whatever I use to achieve this must somehow be tied into the existing QListView signals, yes? Like checking scrolling notifications or the like?
@JMO_GS
Hi
Sorry for being vague.
There is not class for it as such. It would be subclassing the view to be able to catch the events
related to scrolling. For each such event, look if the items actually visible and handle when new ones comes
into view and when some leaves the view ( for unloading)I think I would start with the Delegate and see if laggy as it would give u "unloading" automatically.
-
Hi! Another possibility would be using a custom delegate to render the items. The model would only know the names of the files and the delegates would create the thumbnails automatically once they are shown. Also, once the delegates get automatically destroyed, the thumbnails would get destroyed, too. I think this would result in minimal memory footprint, although the GUI might feel laggy. If the latter should prove to be unacceptable you could use one or more seperate threads for the computation of the thumbnails.
@Wieland The custom delegate proved to be the best approach for me, thanks.
- I just created a class derived from QStyledItemDelegate and installed it to the QStandardItemModel I was already using.
- I overrode it initStyleOption() function. which called the base class version there (which found no icon)
- Then in my derived version, detected this lack of icon and issued an asynchronous request to load it.
- In the meantime, I filled out the QStyleOptionViewItem with a default empty icon and returned this to the caller. So for a brief moment, the user sees an blank square
- When the asynchronous request to load the icon is done, it signals my widget which updates the items icon.
*To make things simpler, I made sure that when I create all of my QStandardModelItems, I give them a custom piece of data (a custom role) that holds the path of the thumbnail to be loaded.
*I have a timer running that periodically checks and unloads non-visible icons. This timer gets reset every time the user scrolls or loads a new icon.
Works quite well. Thanks
-
@Wieland The custom delegate proved to be the best approach for me, thanks.
- I just created a class derived from QStyledItemDelegate and installed it to the QStandardItemModel I was already using.
- I overrode it initStyleOption() function. which called the base class version there (which found no icon)
- Then in my derived version, detected this lack of icon and issued an asynchronous request to load it.
- In the meantime, I filled out the QStyleOptionViewItem with a default empty icon and returned this to the caller. So for a brief moment, the user sees an blank square
- When the asynchronous request to load the icon is done, it signals my widget which updates the items icon.
*To make things simpler, I made sure that when I create all of my QStandardModelItems, I give them a custom piece of data (a custom role) that holds the path of the thumbnail to be loaded.
*I have a timer running that periodically checks and unloads non-visible icons. This timer gets reset every time the user scrolls or loads a new icon.
Works quite well. Thanks
