https://bugs.kde.org/show_bug.cgi?id=399600
--- Comment #4 from IWBR <iwannaber...@gmail.com> --- Well, yep, it's based on this bug, but here I focus on the fact that the library can differ from the picture metadata because digikam (and users) thinks these changes have been applied when they have not. For instance, imagine one user correcting the date on one picture. He hits on apply, the change is reflected in digikam, so he considers the job is done. But internally, digikam found the file is read-only, didn't apply any changes, and shows mismatching information that won't be updated to other people (which might use digikam or other software to view those pictures). As I said, just re-scanning metadata when files have been modified should solve this issue. Plus the read-only warning (or greying-out the OK and Apply buttons, I don't know, but at least some feedback would be helpful). -- You are receiving this mail because: You are watching all bug changes.
