[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: Blue scary screen
From:       Tom Albers <tomalbers () kde ! nl>
Date:       2005-12-15 17:29:35
Message-ID: 200512151829.43596.tomalbers () kde ! nl
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/mixed)]


Hi Ingo,

Op donderdag 15 december 2005 00:32, schreef u:
> On Wednesday 14 December 2005 23:52, Tom Albers wrote:
> > Hi,
> >
> > I hope you will not hate me for this, but I want to point to
> > http://bugs.kde.org/show_bug.cgi?id=116773
> >
> > The blue screen which appears when selecting folders shows up on
> > whenever I switch to another folder. When I'm home or at work does
> > not make a difference, it is on every single change.  I can not start
> > to explain how irritating this behaviour is.
> >
> > I'm not sure how this has improved usability in any way, but
> > discussing that will not be very productive.
>
> If (seemingly) nothing happens after the user selected a folder he'll
> wonder whether he did something wrong. The progress screen shows the
> user that KMail is doing something. Whether a 1 second timeout is too
> short or not is of course debatable.

What I do not understand is why there are four ways to tell the user what is 
going on:
1) status bar 
2) progress bar in the status bar
3) the progress bar in the popup as shown when forwarding a message which is 
not completely retrieved yet
4) the blue scary screen

One of the objections is that 'we' are now learning the user not to look at 1) 
or 2) when something takes longer then expected. I hope it does not set an 
example for everything that lasts a bit longer.

> > I'ld like to know if
> > attached patch is acceptable. If not, I'll close the br and start to
> > compile kmail manually with a similar patch, because I really would
> > like to use KMail again.
>
> Sorry, but a 10 second timeout is not acceptable. If you want to invest
> a little bit more time on this then you can make the timeout
> configurable 

Thanks for the hints, attached is the patch based on that. Do I need to take 
care of trunk or can someone forward port it? Can I document the hidden 
setting somewhere (wasnt there a wiki page for that)?

Tom
Please cc me on replies...

["kmail.kmmainwidget.diff" (text/x-diff)]

Index: kmail.kcfg
===================================================================
--- kmail.kcfg	(revision 488698)
+++ kmail.kcfg	(working copy)
@@ -177,6 +177,9 @@
     </group>
 
     <group name="Internal">
+      <entry name="FolderLoadingTimeout" type="Int" hidden="true">
+         <default>1000</default>
+      </entry>
       <entry name="MsgDictSizeHint" type="Int" hidden="true">
         <default>9973</default>
       </entry>
Index: kmmainwidget.cpp
===================================================================
--- kmmainwidget.cpp	(revision 488698)
+++ kmmainwidget.cpp	(working copy)
@@ -1787,10 +1787,10 @@
       mForceJumpToUnread = forceJumpToUnread;
 
       // Set a timer to show a splash screen if fetching folder contents
-      // takes more than a second
+      // takes more than the amount of seconds configured in the kmailrc (default 1000 msec)
       mShowBusySplashTimer = new QTimer( this );
       connect( mShowBusySplashTimer, SIGNAL( timeout() ), this, SLOT( slotShowBusySplash() ) );
-      mShowBusySplashTimer->start( 1000, true );
+      mShowBusySplashTimer->start( GlobalSettings::self()->folderLoadingTimeout(), true );
       return;
     } else {
       // the folder is complete now - so go ahead

["smime.p7s" (application/pkcs7-signature)]

_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]