https://bugs.kde.org/show_bug.cgi?id=372781
--- Comment #5 from Mario Frank <mario.fr...@uni-potsdam.de> --- (In reply to caulier.gilles from comment #4) > >I do not think that accessing the digikamrc from different classes > >(DublicatesFinder, FindDuplicatesView and MaintenanceMgr) is a really good > >solution since it leads to much code. > > It's not a problem. We have ApplicationSettings class singleton dedicated > for that. > > https://cgit.kde.org/digikam.git/tree/libs/settings > > > >I thought about using the Settings table > >of the database since the access is straightforward. > > No this is not the right way to do... > > Gilles Caulier Hey Gilles, many thanks for this hint. This makes it quite convenient to work with the configuration. I adopted my patch yesterday eve. Now, I save the last minimum and maximum similarity in the Duplicates Search View section of the digikamrc. I could have opened a new Section. But these configuration values are used only in the Duplicates Search View. So I don't want to open a new section only for those two values. -- You are receiving this mail because: You are watching all bug changes.
