I feel compelled to comment again. I agree that tiered timings seem like a good compromise between uniformity and flexibility for developers. The current timing has led to my disabling notifications in several applications, but really it's more than the timing. It's a coupling of timing and location: Inability to customise timing makes a potentially inconvenient placement worse. Inability to customise location makes a potentially inconvenient timing worse.
I think there's general agreement that notifications are useful to people and that the present system is transient in favour of a future, better solution. Thinking well inside the box here, it seems as though customisable timing represents a less arbitrary option. That is, placement is something coders probably don't care about and something non-coders can adapt to. Timing is something that coders do care about and something which can, if used appropriately, improve a user's experience. Tiered timing (short, medium, and long-duration messages) provides a means of enforcing a degree of timing uniformity while allowing that flexibility. I'll now install that Leolik PPA. -- 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
