Think this discussion has gone on too long and is going nowhere. It
needs to be reviewed.

1) Clearly developers have a need to be able to override the default
time of the notification. That needs to be considered, especially if you
want to encourage development on the platform.

2) If you're not going to allow it to be ovverrideable, then remove the
option from the documentation! Save some of the confusion.

3) My preference would be making it overrideable. There's a system
default, which Ubuntu can follow, but 3rd party apps have the ability to
override (based on some of the use cases mentioned). If you feel this is
inconsistent, that's ok... **You don't have to install the 3rd party
apps!** The user can make that choice, why not let them, rather than
trying to force it on them.

If I for example wrote an app, and set the timeout to 10minutes, I'm
sure users would get annoyed, and uninstall my app.

It reminds of the sort of awful decisions the UK goverment make,
"umbrella" laws/rules that apply to everything but don't work in terms
of interests to the customers, ie the public.

-- 
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to