@Mark: Sorry, that was probably a bit confusing. ;-)
What I meant was the following: Whenever a new batch of images are received
I resize and compress them a little bit to create thumbnails. After the
images are resized and compressed, they are added to the ListModel. That's
the part, that is stil
Hi,
I don't quite follow.
First you say you implemented our suggestions (move image processing in a
thread), then you say: "all operations are performed in the main (GUI)
thread"... Exactly the opposite of what we've been suggesting.
If i'm reading your reply correctly you're not offloading anyt
Yes - it's possible to move QImage processing to another thread. I've used
QtConcurrent::run() to resize and write several images concurrently.
void SomeClass::_writeImage( QImage inImage, const QString &inPath )
{
QFuture future = QtConcurrent::run( [this, inImage, inPath] () {
QImage
you should avoid any time consuming ops in his thread
On Aug 13, 2017 22:40, "Bernhard B" wrote:
> Many thanks guys!
>
> I just implemented your suggestions and have to say that the scrolling
> performance definitely improved a lot. Thanks a lot for your help!
>
> However, as I am now doing more
Many thanks guys!
I just implemented your suggestions and have to say that the scrolling
performance definitely improved a lot. Thanks a lot for your help!
However, as I am now doing more work (compress image + resize) before I
populate the Listmodel, I noticed that there is a significant lag eve
