Comment 83 for bug 390508
Revision history for this message
| wirespot (wirespot) wrote Re: notify-send ignores the expire timeout parameter | #83 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@Sebastian Bacher:
> 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
So draw up a set of HIG guidelines and kindly ask developers to apply them WHEN they make sense. There's no such thing as an interface that's 100% perfect for everybody and everything all the time.
Nothing is solved by hardcoding such limitations. People who want to bypass the limitations will still do so, while legitimate use cases will not be catered to.
> and wouldn't work with the notify-osd slots design (ie
> notifications don't get stacked but use the same location).
I fail to see how a shorter timeout would affect stacking. Or why shorter timeouts mean we must eliminate stacking, if that's what seems to be implied above.