Comment 88 for bug 390508
Revision history for this message
| Holger Berndt (berndth) wrote Re: notify-send ignores the expire timeout parameter | #88 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Guys, you just don't seem to get that notify-osd is about unification and consistency amongst applications using it. It's fundamental design point is to NOT allow applications to use it in different ways, and also not to let the user configure it extensively. In this light, what you request as a feature, could actually be regarded as a bug if it was implemented.
As a user, you are free to use an alternative implementation of the D-Bus spec that suits your needs better.
As a programmer, you have to deal with the behaviour of possible implementations on your target platform. You just cannot rely on specific timeouts, or specific behaviour. In fact, you can't even rely on your notification being visible at all. The notification daemon could just as well not display anything, but write the message to a log file (which obviously never times out).
If that's a problem to your usecase, you probably shouldn't be using the notification infrastructure for it in the first place. That would be a design-bug in your own code, then.