https://bugs.kde.org/show_bug.cgi?id=384092
--- Comment #6 from caulier.gil...@gmail.com --- The only differences here to touch file : - Exiv2 CLI : on thread (one process in fact) - digiKam C++ API : multi-threaded as GPS editor use QFuture internaly as i remember. No more. digiKam do not touch the file as well. All is delegate to Exiv2 core. So the internal Exiv2 implementation must be re-entrant and thread safe. It's mandatory. The digiKam implementation is thread safe of course as all digiKam use multi-threading everywhere, when it's possible. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
