[Digikam-devel] [digikam] [Bug 320359] SCAN : digiKam should show which directories are scanned during start-up when adding collections after database deletion

[via KDE Bugzilla]

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

caulier.gilles at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/4047edd1532b129fe895a8c
                   |                            |4b0f810adc92d2f7f
         Resolution|---                         |FIXED
   Version Fixed In|                            |5.1.0
             Status|CONFIRMED                   |RESOLVED

--- Comment #8 from caulier.gilles at gmail.com ---
Git commit 4047edd1532b129fe895a8c4b0f810adc92d2f7f by Gilles Caulier.
Committed on 18/07/2016 at 12:48.
Pushed by cgilles into branch 'master'.

Improve digiKam startup time :
------------------------------

- remove splashscreen from ScanController. Always use a progress dialog instead
in all cases.

- We will always require a progress dialog at first init to scan albums.
All details are given in dialog about which album is scanned and how many items
still in the queue to process.

- The splashscreen always arrive after the progress dialog. Splash show final
stage to init GUI

- When GUI is displayed, always start a delayed find new item process through
progress manager. This is done in background.
Progress info is given in progress manager as well. While scan for new item is
running in a separated thread,
user can start to work with GUI, even if all items are not yet catalogued in
database.
Related: bug 281959
FIXED-IN: 5.1.0

M  +18   -29   app/main/digikamapp.cpp
M  +9    -42   libs/database/utils/scancontroller.cpp
M  +2    -3    libs/database/utils/scancontroller.h
M  +4    -2    utilities/maintenance/maintenancetool.h

http://commits.kde.org/digikam/4047edd1532b129fe895a8c4b0f810adc92d2f7f

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