KDirModelV2, KDirListerV2 and UDSEntryV2 suggestions

[Alexander Neundorf]

On Thursday 10 January 2013, Mark wrote:
...
> > * DirModel::updatePreview calls setData for each preview that it gets
> > back. that causes dataChanged to be emitted. again, for each index. this
> > needs to be batched up and/or DirModel should override data() itself to
> > return Qt::DecorationRole when it has a preview.
> 
> Would a 300ms timer be acceptable in user experience? So if there are
> new thumbnails available, batch them and update the model only once
> every 300ms. Or is 300ms too much?

I think usually they say that it is around 100ms when people are starting to 
notice lags. 300ms is clearly above that.
I think people will see the 3 updates per second, while 10 updates per second 
may look like continuous updating.
100ms is still a very long time for a CPU.

Alex