--nextPart5245545.tDb1p6CQXp
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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 ru=
n=20
out of battery and might prefer hibernating over unclean system shutdown du=
e=20
to powerloss.

I am pretty sure you can configure powermanagment to just notify you and no=
t=20
take any action.

I agree with the others that application developers need to understand the=
=20
configurability of notifications anyway and that the notification server ca=
n=20
either just drop the actions or, like KNotify, offer respective alternative=
s.

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

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart5245545.tDb1p6CQXp
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBKnWKnnKMhG6pzZJIRAso9AJ9lwl06MUCAdVYBy5VLKQME13JmdwCeN6JJ
6XZB/U4ZxviCj91SGqZa5A0=
=JMjI
-----END PGP SIGNATURE-----

--nextPart5245545.tDb1p6CQXp--