From kmail-devel Sun Aug 10 20:41:40 2003 From: Andreas Gungl Date: Sun, 10 Aug 2003 20:41:40 +0000 To: kmail-devel Subject: Re: [PATCH] ClientInterface (next try) X-MARC-Message: https://marc.info/?l=kmail-devel&m=106054795920574 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1658566082878393==" --===============1658566082878393== Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_Z4qN/ya3hP/rwfw"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit --Boundary-02=_Z4qN/ya3hP/rwfw Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Monday 28 July 2003 00:55, Ingo Kl=F6cker 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=20 suitable solution to move the Yes-No-MessageBox towards the client side.=20 Unfortunatly the whole code is processed asynchroneously, i.e. whatever the= =20 boolean result in KMSender::send(...) resp. KMSender::sendQueued() is - it= =20 doesn't reflect whether the sending was successfull. The only thing you=20 know is whether the sending has been started or not. Okay, the basic idea behind the question to the user is: Should the sending= =20 get stopped after an error or should the next waiting message be given a=20 try. To avoid the requested feedback from the user I would like to change=20 the behaviour to the following: When an error occured and there are still other messages ready to send, the= n=20 inform the user about the error and tell him explicitly that KMail will try= =20 to send the other messages plus that he can abort the sending by=20 him/herself. IMO the user is able to stop the sending using the button in=20 the status bar. This is no perfect solution and a step backward compared to= =20 the current state, but I think it's a valid compromise for the goal I'm=20 working on. Perhaps someone else has a better idea. So before I proceed I wanted to=20 discuss this issue on this list. I'm looking forward to your feedback. Andreas =2D-=20 ~ ' v ' // \\ /( )\ Powered by Penguin. ^ ' ^ --Boundary-02=_Z4qN/ya3hP/rwfw Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQA/Nq4ZVhjiFd4beU8RAqmsAJ48Bhn2ViFT6lEYVL7rhPuFBAlOawCg5p9I HG0WITeSxjQQg4HtdtZuhCQ= =CHrL -----END PGP SIGNATURE----- --Boundary-02=_Z4qN/ya3hP/rwfw-- --===============1658566082878393== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KMail Developers mailing list kmail@mail.kde.org http://mail.kde.org/mailman/listinfo/kmail --===============1658566082878393==--