| Summary: | Renaming or reordering tags does not respect the "Use lazy synchronization" option. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Paul Krause <paul_krause_1980> |
| Component: | Tags-Manager | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | minor | CC: | caulier.gilles, metzpinguin, paul_krause_1980 |
| Priority: | NOR | ||
| Version First Reported In: | 8.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Krause
2021-02-21 21:06:53 UTC
There are other tasks in digiKam where we have to ignore lazy synchronization, e.g. also when writing faces (after image rotation). The problem here is that when you rename tags, they have to be written into the images. If a re-read of the metadata were triggered by an external process or an internal copying process, a previously deleted or renamed tag would re-appear in the tag tree. Everything cannot be postponed until later with lazy synchronization. Maik Dear Maik, your objections are clearly valid. Unluckily I do not share them personally, but please correct me if I'm wrong. I) I can mess up my tags anyway already. By selecting No on the "write XXX items later" dialog, regardless of the lazy synchronization option. So why not give the user this option consistently for any number of items? Maybe as an additional sub-option beneath lazy synchronization? II) Additional I wish for changing 2b): Selecting No on the "write XXX items later" dialog, or if lazy synchronization would be respected, should add these items to the metadata write queue. At the moment nothing happens. Thus the writing of the metadata is not only postponed until later, but indefinitely until some other request for metadata writing is done for these items. Thank you very much! Paul Paul, I suppose that problem still present in 8.0.0 ? Gilles Caulier |