Version: 0.9.1 svn (using KDE KDE 3.5.6) Installed from: SuSE RPMs OS: Linux When starting digikam (both stable and svn versions) it always takes a while until the program gives some feedback to the user that it's about to start. I'd recommend to display the splash screen as the very first thing digikam does (just as most of all other apps do). This is nothing important, but especially not-so-experienced users with not-so-fast computers might think the program didn't start when they don't get feedback right after the click.
Hi Daniel, Are you enable the "Scan at Startup" option ? Can you take the time mesurement between the digiKam binary start to run from a console, and the splash appear on the screen. Can you identify witch operations are done on the console before to show the splash. Nota : if you disable the debug compilation option, you will speed-up digiKam Gilles 3 Mar 2007 17:57:41 -0000, Daniel Bauer <linux@daniel-bauer.com>: [bugs.kde.org quoted mail] <div>Hi Daniel,</div> <div> </div> <div>Are you enable the "Scan at Startup" option ? Can you take the time mesurement between the digiKam binary start to run from a console, and the splash appear on the screen. Can you identify witch operations are done on the console before to show the splash. </div> <div> </div> <div>Nota : if you disable the debug compilation option, you will speed-up digiKam</div> <div> </div> <div>Gilles <br><br> </div> <div><span class="gmail_quote">3 Mar 2007 17:57:41 -0000, Daniel Bauer <<a href="mailto:linux@daniel-bauer.com">linux@daniel-bauer.com</a>>:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">------- You are receiving this mail because: -------<br>You are the assignee for the bug, or are watching the assignee. <br><br><a href="http://bugs.kde.org/show_bug.cgi?id=142469">http://bugs.kde.org/show_bug.cgi?id=142469</a><br> Summary: splash screen to be the very first thing<br> Product: digikam<br> Version: unspecified <br> Platform: SuSE RPMs<br> OS/Version: Linux<br> Status: UNCONFIRMED<br> Severity: wishlist<br> Priority: NOR<br> Component: general<br> AssignedTo: digikam-devel kde org <br> ReportedBy: linux daniel-bauer com<br><br><br>Version: 0.9.1 svn (using KDE KDE 3.5.6)<br>Installed from: SuSE RPMs<br>OS: Linux<br><br>When starting digikam (both stable and svn versions) it always takes a while until the program gives some feedback to the user that it's about to start. <br><br>I'd recommend to display the splash screen as the very first thing digikam does (just as most of all other apps do).<br><br>This is nothing important, but especially not-so-experienced users with not-so-fast computers might think the program didn't start when they don't get feedback right after the click. <br>_______________________________________________<br>Digikam-devel mailing list<br><a href="mailto:Digikam-devel@kde.org">Digikam-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/digikam-devel">https://mail.kde.org/mailman/listinfo/digikam-devel </a><br></blockquote></div><br>
Hi Gilles, yes I have enabled "Scan at Startup", and the box with the database scan messages appears before the Splash-Screen. I have version 0.9.0 (stable, from suse rpms) and 0.9.1 svn. I've stopped the times and it seems that the start time until database scan box appears depends on the mood my computer feels :-) - when I start 0.9.0 for the first time after booting my computer with typing "digikam" into console there are no messages and it takes 50 seconds until the message box appears. There are no messages in console during that time. - when I then start 0.9.1 svn with the start-digikam.sh script it takes only 5 seconds until that box appears. - when I start 0.9.0 or 0.9.1 again the message box appears almost immediately. However, sometimes it takes much longer also with 0.9.1 svn (probably depending on what else my computer is doing at the same time or what parts are already loaded). As said in my first post, I don't consider this wish as anything important, just thought it could be possible to move the display of the splash screen right to the beginning of the start routines of digikam - if you have too much time and nothing else to do :-)) But I have no complaints about digikam speed at all. Maybe its really just a matter of how my computer likes to work or not :-) regards Daniel
Daniel, Splashscreen is a non user-interaction window (no button). Scan dialog at startup can be canceled by the user. This is why both are displayed by different way. For me, there is no reason to change it. digiKam always report progress at startup in all case. Gilles Caulier
Hi, I have to say I agree with Daniel. Starting digikam the first time can take a long time before getting some startup dialog (on a slow computer with around 10'000 pictures, it's more than 30s). Daniel: once digiKam has be launched a 1st time, it's much faster because linux caches disk access in memory... If digiKam has been compiled with debug and is run from command line, you can see something, but otherwise you just have to wait. It could be a problem : I already saw somebody from my family clicking 3 or 4 times because nothing was displayed. And after one minute, you get as many instances :) IMHO, it would be great to display the splash screen at the very beginning, then you can still show the scan window above the splash screen...
Marcel, Any objections ? Gilles Caulier
Hi :-) I personally don't care... but friends of mine (who do no use digiKam on a daily basis) sometimes think that they haven't started digiKam or not clicked properly and then click again and wonder that nothing happens... I know, this appears only the first time after boot. I just thought it would be nice if the splash screen appears immediately after clicking the icon. For sure it's not important. But if it's a small change in the code, I'd suggest to do it :-) regards Daniel
Ok, i reopen bug. Gilles Caulier
SVN commit 787653 by cgilles: digiKAm from KDE3 branch : show splashcreen just before to scan whole albums to imediatly give to users program activity. BUG: 142469 M +11 -2 digikamapp.cpp M +1 -9 main.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=787653
Fabien, Arnd, Marcel, Mik, Gerhard, This unsignifiant patch solve this issue. But please check if all work fine on your computer to : 1/ rename temporally your digiKam DB file on your root path and start digiKam, to simulate a first start 2/ close digiKam and restart it to check again. Note than now the Scan Dialog is displayed over the splashscrenn during all scan albums process. This is fine for you ? Gilles Caulier
All works fine. However, the Scan Dialog is displayed behind the splashscreen (and scanning was too fast to bring that window to the front ...); I suspect that this depends on the window manager.
I recompiled everything and did all tests. It works perfectly. And for me, the scanning dialog is displayed over the splashscreen. It looks good. Thanks !
> Note than now the Scan Dialog is displayed over the splashscrenn during > all scan albums process. This is fine for you ? Works fine.
Marcel, Patch is now backported to KDE4... It will be nice if later we can merge scan dialog to splashscreen if splashscreen is enable. Else standard scan dialog is used instead. What do you think about ? Gilles
Yes, I dont particularly like the scan dialog. For example, we could show a progress message "scanning collection" inside the splash screen and only show a scan dialog if the scanning takes longer than a few seconds, then hiding the splash screen for the time, or even creating a scan dialog that is visually similar to the splash screen.
Yes, but if splash is disable from settings, scan dialog is mandatory to show progress... There are also anither point with scan dialog : if user close it, scan is stopped as well... Gilles
SVN commit 788153 by cgilles: digiKam from KDE3 branch : - if Splashscreen is enable at startup, do not show Scan dialog and post progress to Splash - If Splashscreen is disable, use Scan dialog. CCBUGS: 142469 M +3 -2 albummanager.cpp M +2 -1 albummanager.h M +4 -2 digikamapp.cpp M +12 -6 scanlib.cpp M +7 -3 scanlib.h WebSVN link: http://websvn.kde.org/?view=rev&revision=788153
SVN commit 788171 by cgilles: backport commit #788153 from KDE3 branch CCBUGS: 142469 M +1 -1 digikamapp.cpp M +29 -11 scancontroller.cpp M +4 -3 scancontroller.h WebSVN link: http://websvn.kde.org/?view=rev&revision=788171