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

List:       kde-usability
Subject:    Re: Fwd: Re: KMail annoyance
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2003-12-13 15:58:44
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Saturday 13 December 2003 15:50, Waldo Bastian wrote:
> On Sat December 13 2003 11:57, Ingo Klöcker wrote:
> > On Saturday 13 December 2003 16:38, Alexey Arzamasov wrote:
> > > On Saturday 13 December 2003 08:34, Till Adam wrote:
> > > > In short, I think the feature is fine and not annoying,
> > > > provided the word "patch" is removed from the default word
> > > > list. Developers can easily add it again.
> > >
> > > They may say that the word "patch" was the main cause of having
> > > this functionality :)
> >
> > Well, Till is a developer. ;-)
> >
> > > Actually, user can switch it off without searching through the
> > > config dialogs - when it triggers you can disable it at the place
> > > by checking the "do-not-annoy-me" checkbox.
> >
> > The dialog had such a checkbox for a very short time. But it was
> > removed again because it doesn't work correctly since the dialog
> > remembers your last decision. (All dialogs with a "do-not-annoy-me"
> > checkbox do this.) So if you checked the checkbox _and_ selected
> > Add Attachment (or whatever the button is called) then the next
> > time the dialog would have to be shown automatically "Add
> > Attachment" would be assumed as the user's answer and therefore the
> > user would be trapped in an endless loop (until he either adds an
> > attachment or removes any occurrence of the "attachment" keywords
> > from his message).
>
> This can be easily overcome by manually checking with
> "KMessageBox::shouldBeShownYesNo()" before calling the messagebox and
> then not making the KMessageBox call at all if it should not be
> shown.

I didn't knew about this function. But the problem is that it's 
impossible (with the KMessageBox API) to get this in sync with the 
setting in the Composer->Attachments section of the configuration 
dialog because there is no KMessageBox::resetDontShowAgainYesNo() 
method which would remove the config entry in case the user re-enables 
the attachment warning. Of course we can manually delete the 
corresponding entry from the "Notification Message" group, but then we 
can as well simply read the corresponding entry and don't need to call 
KMessageBox::shouldBeShownYesNo() just to check whether there is an 
entry. The lack of reset... methods is IMO a flaw in the API. Should I 
prepare a patch which adds these methods?

Regards,
Ingo

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

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


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