Comment 74 for bug 390508

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: notify-send ignores the expire timeout parameter

Seems some people feel strongly about the subject, nobody is being arrogant there but you are discussing at the wrong place since designers will not follow every bug reports which are usually about technical issues or bugs in the code writte. You should raised the topic on the ayatana list for discussion.

Note that the fact that you want to be able to use random timeout in softwares would lead the system to behave in an inconsistant way tiiming wisz and wouldn't work with the notify-osd slots design (ie notifications don't get stacked but use the same location).

> Either it should support merging, replacement, and stacking, or notify-osd should support the timeout option. This is just common sense.

The current system does support appending or replacing, see what the default im client or music player do in lucid. If you want to display a note for ever on screen why don't you just open a dialog to display it?

You should maybe come with concrete example of things that the current design is limiting which would benefit users (displaying some bubbles for 6 seconds and some others for 8 seconds because software writters don't agree between themself would not benefit users) and raise the topic on the ayatana list for discussion