Thumbnail View

[wysota]

Have a list of instances of a structure, you might want to add some more info later and there is no point in redesigning everything then. Or just use QStandardItemModel.

[MTK358]

That's a good idea. The problem with QStandardItems is that it must store the whole path, but show only the name in the view.

Also, how do I avoid starting huge amounts of the concurrent thumbnail functions at once? Or is it OK?

[wysota]

The problem with QStandardItems is that it must store the whole path, but show only the name in the view.

Sorry? There is Qt::DisplayRole for what gets shown and an infinite number of custom roles you can use for any data you want (such as the full path).

Also, how do I avoid starting huge amounts of the concurrent thumbnail functions at once? Or is it OK?

It's ok, they will be queued.

[MTK358]

Sorry? There is Qt::DisplayRole for what gets shown and an infinite number of custom roles you can use for any data you want (such as the full path).

How am I supposed to do that when I'm not using a custom model?

It's ok, they will be queued.

They will be queued automatically without me taking any action?

[wysota]

How am I supposed to do that when I'm not using a custom model?

You can pass any integer equal or larger than Qt::UserRole as the role for any method accepting a role identifier.

They will be queued automatically without me taking any action?

Yes. QtConcurrent will only run concurrently at most as many jobs as you have cores available in your machine (so 1 task for 1 core, 2 tasks for 2 cores, etc.), excluding the main execution thread (so Qt Concurrent guarantees that at least one job will be ran). The remaining jobs will be queued until there are idle threads available.

[MTK358]

You can pass any integer equal or larger than Qt::UserRole as the role for any method accepting a role identifier.

So you can add a non-visible piece of data to be used internally by your program to a QStandardItem?

Yes. QtConcurrent will only run concurrently at most as many jobs as you have cores available in your machine (so 1 task for 1 core, 2 tasks for 2 cores, etc.), excluding the main execution thread (so Qt Concurrent guarantees that at least one job will be ran). The remaining jobs will be queued until there are idle threads available.

OK, that's nice.

[wysota]

So you can add a non-visible piece of data to be used internally by your program to a QStandardItem?

Yes, that's correct.

enum { myCustomStringRole = Qt::UserRole+1, myCustomColorRole };
//...
QStandardItem *item = ...
item->setData("my custom string", myCustomStringRole);
item->setData(QColor("red"), myCustomColorRole);

enum { myCustomStringRole = Qt::UserRole+1, myCustomColorRole };
//...
QStandardItem *item = ...
item->setData("my custom string", myCustomStringRole);
item->setData(QColor("red"), myCustomColorRole);

To copy to clipboard, switch view to plain text mode