https://bugs.kde.org/show_bug.cgi?id=423227
--- Comment #7 from caulier.gil...@gmail.com --- Anders, Technically, digiKAm have been a KDE application until 3.0.0 as KIO slave was used to perform serialized database operation. We leaves KIOSlave technology as it's not portable outside Linux. Performance was really bad with large collections. Multithreading was used instead. Step by step we transform digiKam as a pure Qt5 application. It still KDE API used mostly with GUI and main view. digiKam has never shared API with dolphin or other KDE application, excepted for plugin through KIPI. Now this point was also left as we have a pure Qt5 plugin architecture, more simple, and powerful. The problem with album tree-view and drag and drop are probably due to bugs in Qt5 API. Personalty, all work as expected here, i never seen this king of dysfunction here. And i use all the time the D&d features, and it's a pleasure with multi-screens. Note: here you will see the list of KDE API dependencies used by digiKam. As you can see, digiKam always depends of KDE (KF5 components), even if less API calls are used : https://www.digikam.org/api/index.html#externaldeps Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
