https://bugs.kde.org/show_bug.cgi?id=402346
--- Comment #18 from Thomas Debesse <d...@illwieckz.net> --- To sum it up, there are two bugs affecting the digikam configuration on Windows: 1. The digikamrc file is not stored in any digikam configuration parent folder in the generic configuration parent folder (this very bug), this bug lies either in Digikam or the said KDE framework. 2. The digikam configuration parent folder is stored in a disposable parent folder on Windows instead of the correct generic configuration parent folder (bug 382358), this bugs in fact lies in Qt itself. Unfortunately, fixing this very bug will still produce something wrong until bug 382358 is fixed), and we better get Qt 6 fixed instead. I just created the bug on Qt side: https://bugreports.qt.io/browse/QTBUG-129134 Once this bug is fixed on Qt side, using `AppConfigLocation` on Windows will fix both this very bug _and_ bug 382358. Actually using `AppConfigLocation` should be what to do on both Linux XDG, macOS and Windows, but unfortunately Qt wrongly implemented `AppConfigLocation` on Windows because Qt wrongly implemented `GenericConfigLocation` to begin with. I hope Qt will fix that bug soon, and sorry to have failed to report that Qt bug on Qt side before. Unfortunately this may not be an easy task for them because fixing that bug without implementing an automatic migration will make decade of released Qt applications losing track of their original configuration… I can't help but recommend to encourage Qt developers to fix this bug. KDE developers may want to already use `AppConfigLocation` starting with today to fix this very bug but this will require a migration path code on KDE platform too, since there would be two migrations to be done (one on KDE platform for this very bug: moving the configuration file to a subfolder, and one on Qt side: moving the configuration folder to the right place), one may wait for Qt to fix their bug first, or make sure both migrations will never break the other one whatever which one is done first. So yes, KDE platform storing the `digikamrc` file as `AppConfigLocation\digikamrc` should be the solution, but this will still be wrong because of Qt's own bug. -- You are receiving this mail because: You are watching all bug changes.
