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

List:       kmail-devel
Subject:    Re: [PATCH] ClientInterface (next try)
From:       Andreas Gungl <a.gungl () gmx ! de>
Date:       2003-08-10 20:41:40
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 28 July 2003 00:55, Ingo Klöcker wrote:
> The two open issues could maybe also easily be solved by returning an
> error code and letting the UI code ask for the user's decision or the
> password.

Hi,

I went through the KMSender sources for some times. I tried to find a 
suitable solution to move the Yes-No-MessageBox towards the client side. 
Unfortunatly the whole code is processed asynchroneously, i.e. whatever the 
boolean result in KMSender::send(...) resp. KMSender::sendQueued() is - it 
doesn't reflect whether the sending was successfull. The only thing you 
know is whether the sending has been started or not.

Okay, the basic idea behind the question to the user is: Should the sending 
get stopped after an error or should the next waiting message be given a 
try. To avoid the requested feedback from the user I would like to change 
the behaviour to the following:
When an error occured and there are still other messages ready to send, then 
inform the user about the error and tell him explicitly that KMail will try 
to send the other messages plus that he can abort the sending by 
him/herself. IMO the user is able to stop the sending using the button in 
the status bar. This is no perfect solution and a step backward compared to 
the current state, but I think it's a valid compromise for the goal I'm 
working on.

Perhaps someone else has a better idea. So before I proceed I wanted to 
discuss this issue on this list. I'm looking forward to your feedback.

Andreas
-- 
    ~
  ' v '
 //   \\
/(     )\  Powered by Penguin.
  ^ ' ^


[Attachment #5 (application/pgp-signature)]

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail


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