Comment 121 for bug 390508

The short answer from what i've understood of this whole thing is "Ubuntu dev team creates whatever is allowed to use instant-confirmation bubbles" and us private developers are out of luck. I still want to see if the patch put out will work on Lucid and if so, maybe it can be packaged downstream with my particular derivative (I use linux mint)

Holger seems to get annoyed whenever someone questions the dev teams decision, that's why i didn't post this in the bug thread

 Heather L Van Wilde

"True discovery lies in seeing what everyone else sees and finding what no one else has found"

________________________________
From: Kent deVillafranca <email address hidden>
To: <email address hidden>
Sent: Mon, June 14, 2010 7:57:33 AM
Subject: [Bug 390508] Re: notify-send ignores the expire timeout parameter

>From back in post #19 by Matthew Paul Thomas: "volume, brightness, and
eject bubbles are instant confirmation (synchronous) of something you
have done, whereas notification bubbles are not-necessarily-instant
notifications (asynchronous) of something someone else has done."

...so, how does one create one of these instant-confirmation bubbles?
Because the reason I've been complaining is because I want to pop up a
quick notification in response to a keypress. And if there isn't a way
to do that, then why are those three button-pressing confirmations given
special treatment while mine aren't?

--
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a direct subscriber
of the bug.