Summary: | 'Scan for new images' should work on just current folder | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Obi-Wan <obiwan> |
Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.4.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 |
Description
Obi-Wan
2011-01-17 20:17:36 UTC
Well I thought to file a bug report about digiKam not recognizing the changes immediately, not duplicating the same wish...sigh. Anyway, since it's here, would it help to improve the collection scanner to immediatelly recognize changes in files, if it doesn't already? Gilles, Marcel? Detecting new images within a matter of seconds would certainly be acceptable. As mentioned in the other bug, I sometimes have waited many minutes for it to detect a new image before giving up and rescanning my entire collection. F5 triggers a rescan of the current album. For automatic change detection, we rely on a) KDirWatch for file detection on operating system level. There have been undocumented changes in the way the API is supposed to be used between KDE versions, it's sometimes a problem. I've also seen problems here and there b) KIO notification, if any files are copied or moved by KDE technologies. Within this scope, this works reliable afaik No, F5 does not trigger a scan for new files. At least not in 1.4.0, which is what I've got installed. That was suggested in the previous bug report, too. F5 does a "refresh," which is something different. I don't use KDE as a general environment, but I do use a few KDE apps. The photo editing software I'm most frequently using concurrently with digikam is LightZone, a commercial package that pays homage to no specific windowing environment. However, I've noticed the same failure to recognize new files in a reasonable amount of time even when creating them from the shell with the PBM toolkit. *** This bug has been marked as a duplicate of bug 262720 *** Fixed with https://bugs.kde.org/show_bug.cgi?id=262720 |