Very critical notifications can be set to have a non-expiring timeout. This would ensure that they stay visible until the user acknowledges them.
Some people have also talked about writing a notification backlog for important notifications, where an icon in the tray blinks when there's certain notifications you missed. The problem with this is that you really need to have a fine-grained concept of what's important and should trigger the blinking. You could leave it at critical notifications and you might be fine, but these may as well just be set to not disappear by the calling program if it's really important (your battery is going to explode). Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Mon, Nov 10, 2008 at 6:11 AM, Martin Meyer <[EMAIL PROTECTED]> wrote: > I sometimes miss my notifications too.. Would it be possible to > remember notifications that have come through until they are > explicitly acknowledged? We could bind some key to doing this, so that > you press that key when the notification is showing to acknowledge it. > For "missed" notifications, we could leave an icon in the notification > area. When you click that icon it might show you all the > unacknowledged notifications until clicked again. You'd probably need > some button on all the notices to mark them as "acknowledged". > > As a user, there are many things I like to be notified in the way that > libnotification allows. There are also some notifications that you > won't care about missing, such as "now playing song X". I think > notification daemon should be accepted, but I don't think it should be > used for critical notifications (i.e "your battery will explode in 25 > seconds") unless there is some way of pulling up ones you missed. > > For extra points, if the message says anything about parts about to > explode or catch fire, the daemon should generate a png to reiterate > this text and set it as your background :-) > > Cheers, > Martin > > On Mon, Nov 10, 2008 at 8:28 AM, Rodrigo Moya <[EMAIL PROTECTED]> > wrote: > > On Fri, 2008-11-07 at 13:09 +0000, Calum Benson wrote: > >> On 6 Nov 2008, at 17:38, David Zeuthen wrote: > >> > > >> > But not all notifications comes from applications launched by the > >> > user. > >> > For example > >> > > >> > "There is a high probability that one or more of your hard disk will > >> > malfunction within the next 24 hours" > >> > > >> > "Your laptop battery is being recalled" > >> > > >> > "Security updates available" > >> > > >> > I'm not sure where we'd display stuff like this except for using icons > >> > in the notification area. > >> > >> Some sort of status icon change with an appropriate tooltip would > >> probably be sufficient for things that don't need immediate > >> attention. For things that do, or for which there is no status icon, > >> an alert box is often more appropriate anyway. > >> > > wasn't libnotify/notification-daemon created to replace alert boxes? I > > tend to find them quite useless, since I miss them most of the time > > while typing without looking at the screen, so I don't think they are a > > good solution for immediate attention stuff > > -- > > Rodrigo Moya <[EMAIL PROTECTED]> > > > > _______________________________________________ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > > > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list >
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
