https://bugs.kde.org/show_bug.cgi?id=413837
--- Comment #17 from MarcP <iwannaber...@gmail.com> --- Ok, I see, that option was the source of the problem. But I don't see why it should work this way. In theory, when entering the reverse geocoding tool, it should read the current picture metadata, and not just overwrite it with new tags. I still think it is a bug. In any case, that option is very useful when using a shared picture library. I would say it is a must (other picture managers also work this way by default). If another user changes metadata in a picture (or myself in another computer), I want those changes to be reflected in my database the next scan. Otherwise, my database can be populated with metadata that the pictures don't actually have. I want my library to be a 1:1 reflection of the contents of all the pictures. -- You are receiving this mail because: You are watching all bug changes.
