https://bugs.kde.org/show_bug.cgi?id=416213
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|8.0.0 |8.4.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #19 from MarcP ---
Hi. Yes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #18 from caulier.gil...@gmail.com ---
Hi all,
The digiKam 8.4.0 Appimage bundle pre-release is now based on last modern
frameworks Qt 6.7.0 and KDE 6.2.0.
File can be downloaded at usual place : https://files.kde.org/digikam/
Take a care
https://bugs.kde.org/show_bug.cgi?id=416213
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|7.0.0 |8.0.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #17 from MarcP ---
Yes, this is still relevant.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #16 from caulier.gil...@gmail.com ---
@MarcP
digiKam 8.0.0 is out. This entry still valid with this release ?
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #15 from caulier.gil...@gmail.com ---
Thanks for the feedback Marc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #14 from MarcP ---
This problem still exists, but has a difficult solution because face rectangles
cannot store a hierarchy.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #13 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:
https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
We need a fresh feedback on this file using this version.
Best Regards
Gilles
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #12 from MarcP ---
I just realized that this behavior is likely the cause of Bug 392008. Maybe
they can be even considered duplicates.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #11 from MarcP ---
I know. I remember in the GSoC2019 we faced that dilemma. We could leave the
hierarchy just for regular tags, and display all People in a flat list, sorted
alphabetically (like in Picasa). But a tag tree for People is
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #10 from Maik Qualmann ---
Another thing, if you want to separate tags and face tags, you should no longer
use sub-tags, because there is no way to save this tag path in the images. But
I find a face tag list without sub-tags bad. In your
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #9 from MarcP ---
As far as I know, Picasa treats faces and tags separately (I remember having to
sync them every time, manually), but it doesn't have any kind of tag hyerarchy,
just a flat list for everything. So it's not as advanced as
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #8 from Maik Qualmann ---
The problem is, it's the standard. I have a image here that was processed by
Picasa with faces. In addition to the metadata entry of the face rectangles
with the names of the faces, there is also the tag list with
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #7 from MarcP ---
This is what I thought. In the metadata, people tags have no path. It can use
the path of the regular tag, but you can never be sure that the user did not
also want to keep that person there, at the root of People, so you
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #6 from Maik Qualmann ---
This is difficult to fix. We cannot just delete the tag, it could be linked to
other images. In addition, people names have no path. If the name is found
among people tree, it is used.
Maik
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #5 from Maik Qualmann ---
Git commit 1d17e816245a1c3c3244b85f89d0e98002b92f77 by Maik Qualmann.
Committed on 13/01/2020 at 21:09.
Pushed by mqualmann into branch 'master'.
we need the tag ID and not the image ID
M +1-1
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #4 from MarcP ---
Oh, that is already with the option "Clean up the metadata from the database
when rescan files" activated. I activate it when I want to sync the library in
two computers.
Regular tags get cleaned up. Tags containing
https://bugs.kde.org/show_bug.cgi?id=416213
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #3 from Maik
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #2 from MarcP ---
I am sorry, in Step 5, I meant to say: "5. Start again the FIRST digikam,".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416213
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=416213
--- Comment #1 from MarcP ---
Of course, if you start from a clean database, and you scan the picture after
the tag has been moved, it will only appear in the subtag only. The problem
only appears if the tag already exists at the root of /People, that
https://bugs.kde.org/show_bug.cgi?id=416213
MarcP changed:
What|Removed |Added
CC||iwannaber...@gmail.com
--
You are receiving this mail
23 matches
Mail list logo
