Summary: | Metadata is not correctly updated when just assigning tags | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Andi Clemens <andi.clemens> |
Component: | Metadata-Date | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | marcel.wiesweg |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.2.0 | |
Sentry Crash Report: |
Description
Andi Clemens
2010-03-05 17:01:57 UTC
There is no caching in the metadata tab, it is always directly read from the file. So there should be no additional effect from restarting; selecting another picture and going back should also update the XMP values. The way to update this tab is ImageAttributesWatch::instance()->fileMetadataChanged(url), as called from KipiInterface::refreshImages. Ok, I can reproduce one problem here: When adding a tag with the context menu, all but the last added tag are written to metadata. So when you start with empty XMP and add five tags in a row, the first four will be added. This is the data present in the file itself, not any caching or restarting effect. Assigning from metadata tab is not affected, so it's probably a MetadataManager problem. SVN commit 1102037 by mwiesweg: Make sure that transaction (only needed for sqlite speedup) is finished before emitting for writing. Otherwise, not all changes may have taken effect. (basically indentation changes) CCBUG: 229578 M +27 -23 metadatamanager.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1102037 SVN commit 1102038 by mwiesweg: Use a direct connection here so that cache is invalidated immediately with the change. It's mutex protected. BUG: 229578 M +2 -1 NEWS M +6 -3 libs/database/imageinfocache.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1102038 |