[PATCH] Detecting notification popup server capabilities

Kevin Krammer kevin.krammer at gmx.at
Tue Sep 1 19:06:31 BST 2009

On Tuesday, 2009-09-01, Parker Coates wrote:

> I would agree. If I'm busy and have a lot going on, I have a tendency
> to finish up what I'm doing before looking at notifications,
> especially if I'm expecting them (i.e. downloads in progress, ongoing
> IM conversations). A crucial notification like this could easily get
> missed in that 10 seconds.
> If the computer is going to do something as drastic as hibernate
> itself, I think it should notify me in a much more intrusive, hard to
> ignore way.

It is not going to hibernate out of pure fun, it is doing it because you run 
out of battery and might prefer hibernating over unclean system shutdown due 
to powerloss.

I am pretty sure you can configure powermanagment to just notify you and not 
take any action.

I agree with the others that application developers need to understand the 
configurability of notifications anyway and that the notification server can 
either just drop the actions or, like KNotify, offer respective alternatives.

As I understand the problem right now is that one of the service 
implementations just hardcodes a rather intrusive method instead of doing 
something sensible.
In which case it might make more sense to write a patch for them to handle 
such cases more gracefully.


Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090901/b4d42564/attachment.sig>

More information about the kde-core-devel mailing list