https://bugs.kde.org/show_bug.cgi?id=448789
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from [email protected] --- Hi Maik, Regarding the patch, the logic sound good for me. The only small improvement to do, perhaps, is to fork the loops to a separate thread. As i see that application cursor is turned to pending task, I suppose that loops can take a while if more than one faces must be processed and if the database is busy or access is slow due to network. Using QFuture/QtConcurrent::run() is the most easy way to do, without to cut loops as parallelized future calls, else concurrent access to the database will happen. A simple function called in a separated thread can be enough to not block the whole GUI. Gilles -- You are receiving this mail because: You are watching all bug changes.
