https://bugs.kde.org/show_bug.cgi?id=391856

--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Ahem, I should have 2nd-guessed myself and dump thread IDs from within FMLJ
methods :(

I always thought the list job itself runs on a background thread and thus that
FileManagerListJob::startNextJob() is called on that thread when the class
sends itself the nextJob signal. It inherits KJob after all, and is controlled
via asynchronous methods (if that's the correct term).

So exactly what is running on a background thread here, or should I say, why
does the class inherit KJob if the only background activity is in the
QtConcurrent::run() call?

(BTW, the invokeMethod() call is made after the call into QtConcurrent; I agree
it targets the main thread.)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to