[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2023-05-01 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=448223 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.1.0 Status|REPORTED

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2023-05-01 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=448223 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #7 from Maik Qualmann --- We are in the GUI thread with drag & drop. If we delayed it, nothing would happen during the drop, no message, no change in the tag tree ... nothing that would be particularly problematic. If we wait, we would

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #6 from MarcP --- No worries, it sounds like the kind of thing I would complain about : ) -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #5 from Maik Qualmann --- Ok, it wasn't a bug report from you. ((:-)) Bug 406309 Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #4 from MarcP --- Mmm, I don't remember the exact context now, but I believe consistency in the database/metadata should be more important than user friendliness. In any case, the thing is that the user should not click on the next "Yes"

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #3 from Maik Qualmann --- The problem is not the merging of the tags in the database, this even takes place immediately and in the GUI thread and does not take any time. I remember that we introduced the warning dialog on the basis of a bug

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=448223 --- Comment #2 from MarcP --- Would it be possible to check if all the merges in a batch are non-conflicting (e.g. a future merge is referencing to a tag that has been deleted or merged in a previous merge), and only show one confirmation popup for

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=448223 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik

[digikam] [Bug 448223] Warning ("Another tag with the same name already exists") when merging several tags appears too soon

2022-01-10 Thread MarcP
https://bugs.kde.org/show_bug.cgi?id=448223 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail