[02:33] <kenvandine> mrmcq2u, i don't think i can do anything about that, it is a gnome.org thing
[02:33] <kenvandine> mrmcq2u, however, i think if you have openid you can login to comment
[13:38] <vish> MacSlow: hi...[mac_v here] has Bug #500663 been reported already? can we add it to the notify-osd papercut jam?
[13:38] <ubot4> Launchpad bug 500663 in notify-osd "Notification mouseover behavior is unintuitive" [Undecided,New] https://launchpad.net/bugs/500663
[13:40] <vish> its part of the specs mpt has listed on the wiki
[13:41] <MacSlow> vish, it's not a papercut, but rather a principle design decision
[13:41] <MacSlow> vish, it is?!
[13:41] <vish> MacSlow: yeah
[13:41] <vish> MacSlow: "if a notification bubble has been fully visible for 2000 ms when the pointer enters, it should switch to its mouseover appearance until the pointer leaves, then switch back to its normal appearance and display for a further 3000 ms."
[13:42] <vish> the fix that the user mentions , is basically what mpt mentions [or atleast what i'v understood :) ]
[13:43] <MacSlow> vish, that's not a papercut as it requires some substantial changes in notify-osd due to the timer-observation and especially the extension of the timeout
[13:43] <vish> MacSlow: oh , sure... 
[13:43] <MacSlow> vish, last cycle I started working on that (the needed foundation to actually be able to _extend_ a running timer)
[13:46] <vish> MacSlow: BTW , do you already have a bug where the wifi notifications dont merge? [iirc it was part of what you mentioned to be a papercut bug at the uds]
[13:47] <MacSlow> vish, sounds rather like a network-manager bug (not directly notify-osd)
[13:47] <MacSlow> vish, but a bug-number always helps to get me on your page
[13:49] <vish>  i couldnt find a bug :( .. hence asked ... i'll search harder ;)
[13:53] <vish> MacSlow: ah found it > Bug #501632
[13:53] <ubot4> Launchpad bug 501632 in notify-osd "Wireless network notifications queue up and then display at incorrect times" [Undecided,New] https://launchpad.net/bugs/501632
[14:02] <MacSlow> vish, that's something for mpt/design to figure out first... because it requires a conceptual change
[14:03] <vish> MacSlow: how does the volume notification able to merge the bubbles? as you said it may be the wrong notification send by the nm applet
[14:03] <vish> s/does/is
[14:04] <MacSlow> vish, volume/brightness/eject etc use synchronous (or feedback) notifications... they get displayed immediately (replacing and previous sync. notification if displayed)
[14:06] <MacSlow> vish, normal apps (like nm-applet/network-manager) use asynchronous notifications, which are under notify-osd's queue control, hence the possible difference in notification reception and notification display
[14:07] <vish> MacSlow: could async notifications somehow force the replace? since i'v noticed a wfi bubble when connection is lost and the re-connection do not match with the actual connection status... 
[14:08] <vish> i'd be re-connected but the bubble would still say , "disconnected" ;)
[14:10] <vish> and only after a few secs the bubble would disappear and then say "connected"
[14:14] <MacSlow> vish, async. notifications are not intended for this kind of use.
[14:15] <MacSlow> vish, this issue is not simple to solve
[14:16] <vish> MacSlow: .. yeah , its not a papercut .. but how do we fix this? from notify-osd or from the nm applet end?
[14:17] <vish> asking the nm-applet to send  sync notification instead?
[14:17] <MacSlow> vish, I'm not in "notify-osd mode" right now so cannot give a full view on it
[14:17] <MacSlow> but I feel it needs some conceptual change for network-manager
[14:17] <vish>  lol.. cool
[14:17] <MacSlow> vish, no! nm-applet should _not_ use sync. for that
[14:18] <vish> ok
[14:18] <MacSlow> this is reserved for direct "hardware-feedback" type of things
[14:18] <vish> MacSlow: sure , thanks for clearing stuff up :) 
[14:18] <vish> s/stuff/silly questions
[21:44] <jamalta> Hi, is pynotify the best way to use the new notify-osd from python?
[21:45] <jamalta> Or would it be better to just rely on dbus?
[21:50] <jamalta> Ah, it seems that pynotify is just an abstraction that uses dbus
[22:19] <magcius> Is there any reason revisions 408, 409 is in the karmic branch but not in trunk?
[22:19] <magcius> Of notify-osd, that is
[23:44] <jono> bratsche, where do I set the icon for an app-indicator?