https://bugs.kde.org/show_bug.cgi?id=498798
--- Comment #2 from Jonkeren <josjonke...@gmail.com> ---
Hi Maik. Thanks. Yeah but but but.... :)
The Onedrive folder is not a " virtual placeholder folder" -- the file is saved
just like anywhere else; same file system. The OneDrive exe just scans for
changes / gets file change updates from the OS, and uploads the file(s). That's
it.
So my suggestion was to "kick" the jpg file again from the OS after a change by
Digikam, so that it is correctly registered as a change with the current date
and time. I have a feeling that that's the cause.
Could you please answer my other question still please; the way I understand it
now is that Digikam does not use all parameters of Exiftool, but first "builds"
a command using Exiv2, and then pushes it off to Exiftool? Yes?
Then still, it might be a small thing to check which Exiftool parameters you
used to do the writing. ("-overwrite_original" or
"-overwrite_original_in_place"; or none)
Also; can I see the output log of Exiftool somewhere?
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
