[Bug 263463] New: 'Scan for new images' should work on just current folder

https://bugs.kde.org/show_bug.cgi?id=263463

           Summary: 'Scan for new images' should work on just current
                    folder
           Product: digikam
           Version: 1.4.0
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Database
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Version:           1.4.0 (using KDE 4.5.1)
OS:                Linux

My photo library contains over 100,000 photos spread through over 1000
directories.  I frequently edit images in a different package while digikam is
open, and before I can use the new images in digikam, I must either wait for
digikam to recognize the updated version, or I must scan for new images.
Performing either of these operations on my entire collection takes forever.

It would be really great if there were options for this tool to operate
on just the current folder, which is generally all I really need to have done.
This would dramatically improve the time required to manage my photos!

This feature was requested as part of bug 262720, but was not implemented as
part of the solution to 262720.  Of the two features requested in 262720, this
one would be by far the more beneficial to my workflow.

Reproducible: Always

Steps to Reproduce:
Scan a large collection for new images.

Actual Results:  
Go fix a cup of coffee.  When I return, the operation is done.

Expected Results:  
Stand up and stretch.  When I sit down, the operation is done.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Martin Klapetek]

https://bugs.kde.org/show_bug.cgi?id=263463


Martin Klapetek <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #1 from Martin Klapetek <martin klapetek gmail com>  2011-01-17 20:25:57 ---
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?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=263463





--- Comment #2 from Obi-Wan <obiwan jedi com>  2011-01-17 20:29:47 ---
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.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=263463





--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-01-18 00:30:36 ---
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

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

https://bugs.kde.org/show_bug.cgi?id=263463





--- Comment #4 from Obi-Wan <obiwan jedi com>  2011-01-18 00:53:39 ---
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.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=263463


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|                            |DUPLICATE




--- Comment #5 from Gilles Caulier <caulier gilles gmail com>  2011-12-15 09:49:49 ---


*** This bug has been marked as a duplicate of bug 262720 ***

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=263463

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Scan

--
You are receiving this mail because:
You are the assignee for the bug.