I believe that I can confirm this defect, which is still listed as New. If you take the documented sample that is supposed to show the "correct" way to use append notification, and add a second copy of the notification bubble, you will see that instead of merging the two bubbles, they are independently queued.
--- append-hint-example.py.original 2009-03-26 10:12:06.000000000 +0100
+++ append-hint-example.py 2009-03-26 10:13:00.000000000 +0100
@@ -136,6 +136,15 @@
"Phil owned the place like no one before him!",
"notification-message-IM")
n.show ()
+ n = pynotify.Notification ("Cole Raby",
+ "Hey Bro Coly!",
+ "notification-message-IM")
+ n.set_hint_string ("x-canonical-append", "allowed");
+ n.show ()
+ n.update ("Cole Raby",
+ "Phil owned the place like no one before him!",
+ "notification-message-IM")
+ n.show ()
else:
print "The daemon does not support the append-hint!"
I believe that I can confirm this defect, which is still listed as New. If you take the documented sample that is supposed to show the "correct" way to use append notification, and add a second copy of the notification bubble, you will see that instead of merging the two bubbles, they are independently queued.
--- append- hint-example. py.original 2009-03-26 10:12:06.000000000 +0100 hint-example. py 2009-03-26 10:13:00.000000000 +0100 notification- message- IM") Notification ("Cole Raby", message- IM") append" , "allowed"); message- IM")
+++ append-
@@ -136,6 +136,15 @@
"Phil owned the place like no one before him!",
"
n.show ()
+ n = pynotify.
+ "Hey Bro Coly!",
+ "notification-
+ n.set_hint_string ("x-canonical-
+ n.show ()
+ n.update ("Cole Raby",
+ "Phil owned the place like no one before him!",
+ "notification-
+ n.show ()
else:
print "The daemon does not support the append-hint!"