https://bugs.kde.org/show_bug.cgi?id=267509--- Comment #2 from Marcel Wiesweg <marcel wiesweg gmx de> 2011-03-03 18:59:36 ---
I fully agree we should have some sort of progress indicator on the splash
screen, possibly with a cancel button.
The splash screen goes away very easily, it's enough to click somewhere if you
want to continue work in another app while digikam starts, and it's gone, so
that should perhaps not be taken as any user input.
To fix the underlying issue, there is one thing we can do: The initial startup
scan does some important housekeeping work, like checking for removed files or
directories, and internal cleanup. This is relatively fast. Things get slow
when new files need to be parsed. So it should be possible - at first glance -
to quickly do the housekeeping, start digikam, and do a second round of
new-file scanning in the background.
--
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
Locked
