[Konversation-devel] [Bug 246064] Do not pollute user with notifications when he is aware

[Eike Hein]

https://bugs.kde.org/show_bug.cgi?id=246064





--- Comment #6 from Eike Hein <hein kde org>  2010-07-30 16:32:21 ---
The problem is that the "Configure Notifications" dialog is a standard dialog
from kdelibs and as such not extensible, and putting options related to those
notifications far away from their GUI location into the main config dialog
would be horrible for usability. At the same time I don't see how we could do
this without adding any options -- even the timer thing you suggest above
wouldn't work for those who rely on those events to fire absolutely every time.
I wish KNotify had an built-in ability and option for this: When you fire a
KNotify event you already hand it the window id of the associated window, so it
could check whether the window is active itself. Oh well.

One thing we could do is write a dialog that imitates the "Configure
Notifications" dialog and place a KNotifyConfigWidget inside it along with some
extra options. Also a pretty annoying hack, but far better from a usability
POV.

Actually, with the main config dialog dialog we have going on right now, I
wonder if we could move the KNotify options into the main dialog outright by
embedding a KNotifyConfigWidget, though that would break with the usual KDE
convention of it being a separate menu entry in the menu. But we've had a lot
of user problems with part of the notification options being in one dialog and
the other part in another dialog for some time.

Maybe we could move the KNotify options into the main config dialog, but still
leave the "Configure Notifications" menu item and have it open the main config
dialog on the right page ...

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.