Comment 110 for bug 390508
Revision history for this message
| Heather Van Wilde (heatheriac) wrote Re: notify-send ignores the expire timeout parameter | #110 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
@Holger Berndt
That still comes back to the original problem.
a) To do what you recommend, any application would have to create their own notification system to do exactly what notify-osd does, but is unable to interact with it.
b) While your app (and any other app that has it's own notification system) tries to post at the same time, they either need to use the same notify system or overwrite each other on the screen space
c) A fantastic idea would be a rewrite of the notify-osd type program to better allow integration of numerous messages at once. notify-osd already has the ability built in to show two bubbles at once (for proof of concept, I changed the volume from my keyboard and immediately changed the song using my keyboard in Ryhtmbox. Attaching screen shot)
d) This rebuilt program would still be incompatible with the official notify-osd package, so the official package would have to go.
e) Matt Thomas @ post 29 has already threatened anyone who wants to build a distributable notify program when he said "Ubuntu Software Center will issue a warning if installing it involves uninstalling anything else (such as notify-osd)"
f) That puts us back to the same spot we were in originally. It appears to me that Mozilla is using the specs as the notify-send man page still gives information for using a time-out when sending to it.
At this point, my question would be, how far upstream is this bug? It's obvious that it affects all unpatched Ubuntu derivatives (I use Linux Mint 7 - Gloria). Was the software developed at the Ubuntu level? If so, it might be worth investing in looking for some of these libraries directly from Debian, which if I understand correctly is upstream from Ubuntu.