https://bugs.kde.org/show_bug.cgi?id=460064
Maik Qualmann changed:
What|Removed |Added
CC||mr.dk...@gmail.com
--- Comment #12 from Maik
https://bugs.kde.org/show_bug.cgi?id=460064
Per Wigren changed:
What|Removed |Added
CC||per.wig...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #11 from Jens ---
All the better! :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #10 from caulier.gil...@gmail.com ---
No need to scan twice. If grouped image is associated to an internal tag, this
will be easy to restore as all the relevant code already exist an work well
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #9 from Jens ---
> When a collection is rescanned, you cannot ensure the order of the images.
> How do you want to match an item to the parent item if the parent item hasn't
> even been scanned yet?
The easy solution would be to scan
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #8 from caulier.gil...@gmail.com ---
>It would then have to be something like tag paths?
Right using an internal tags to identify a group of image is the most universal
way, why i don't found this idea myself...
Gilles
--
You are
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #7 from Maik Qualmann ---
Technically it is quite uncertain. When a collection is rescanned, you cannot
ensure the order of the images. How do you want to match an item to the parent
item if the parent item hasn't even been scanned yet? It
https://bugs.kde.org/show_bug.cgi?id=460064
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #5 from Maik Qualmann ---
Grouping is not file metadata. This is a feature within an image management.
How should the link to another image be created in the metadata?
Via the filename/path - is ambiguous.
Via the internal image ID - is
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #4 from Jens ---
Thanks for making this clear.
So what alternatives exist?
I think that being able to transfer albums / folders / files between Digikam
installations including *all* file metadata is a valid use case.
But currently, at
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #3 from Maik Qualmann ---
No, the Metadata Standard does not consider such a use case.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460064
--- Comment #2 from Jens ---
I can agree with you for folder settings.
But I disagree for file groups.
A relationship of a file to another file - like versioning, series shots, edits
or "parent/child" relations - should be portable between apps and is
https://bugs.kde.org/show_bug.cgi?id=460064
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
13 matches
Mail list logo