Open GoogleCodeExporter opened 9 years ago
Yeah, I knew about that, and it is indeed caused by the fact that I calculate
coordinates before the tray icon is shown (it is there, but hidden). I did not
know
how to fix this so far :|
Original comment by nekoh...@gmail.com
on 16 Feb 2007 at 8:20
hey. I actually fixed this in SVN revision 108 or something like that!
Original comment by nekoh...@gmail.com
on 30 Jun 2007 at 7:28
Original comment by nekoh...@gmail.com
on 18 Mar 2008 at 2:06
needs reverification, as the current solution is a hack. The only way I had to
"fix"
this was an ugly workaround: waiting 1 second before sending out the
notification
toast, "hoping" that the tray icon would have had the time to appear by then and
provide me with coordinates. According to Colins Walters, "this should be fixed
now
assuming that you are associating the notification with the status icon".
blog post: http://cgwalters.livejournal.com/17495.html
gtk patch: http://bugzilla.gnome.org/show_bug.cgi?id=535303
notification-daemon patch:
http://cvs.fedoraproject.org/viewcvs/devel/notification-daemon/notification-daem
on-positioning.patch?rev=1.1&view=markup
libnotify patch:
http://cvs.fedoraproject.org/viewcvs/devel/libnotify/libnotify-send-xid-2.patch?
rev=1.1&view=markup
So basically, we need to figure out how to "associate" the notification toast
with
the notification icon.
Original comment by nekoh...@gmail.com
on 20 Jun 2008 at 2:34
Original comment by nekoh...@gmail.com
on 20 Mar 2009 at 12:25
This 1) is a minor defect 2) may not be as relevant since notify-osd 3) may
become
entirely irrelevant when gnome 3.0 comes out with a new notification paradigm.
Thus, lowering the priority as we need to wait and see, I guess.
Original comment by nekoh...@gmail.com
on 8 Nov 2009 at 9:08
Original issue reported on code.google.com by
beer...@gmail.com
on 16 Feb 2007 at 5:38