[Freewx-maint] Bug#745887: libwxgtk3.0-0: Please enable support for libnotify

Christian Beier dontmind at freeshell.org
Tue Apr 29 09:59:45 UTC 2014

Am Mon, 28 Apr 2014 23:35:57 +0100
schrieb Olly Betts <olly at survex.com>:

> A very quick poke at the source found me this behavioural difference in the
> Show() method:
> |       @note When using native notifications in wxGTK, the timeout is ignored
> |           for the notifications with @c wxICON_WARNING or @c wxICON_ERROR
> |           flags, they always remain shown unless they're explicitly hidden
> by |           the user, i.e. behave as if Timeout_Auto were given.
> That's an example of a feature we'd lose, though it's probably not going to
> upset anyone.  But it would be prudent to do a more thorough check.

Ah, that note is in interface/wx/notifmsg.h. Looking at the actual
implementation in src/gtk/notifmsg.cpp, I see that depending on the flags
passed in, icon and urgency are set. The setting of the timeout is independent
from those flags. However, notifications with urgency critical ignore the
timeout, right (tested with the send-notify cmdline tool).

Other than this, I can't seem to find any other issues. With the libnotify
implementation, one can set title, message, timeout (with above exception),
show the notification and manually close it as well. SetParent() function is
not used, but this one doesn't hurt as users expect notifications at the same
spot on the desktop and not at random x,y coordinates.

> > And the libnotify one, which IMO integrates far better with the desktop
> > environment:
> I'm not disputing that it integrates better.

Okay, fine. If the decision is between getting above timeout functionality
exactly as wanted by the wx developers or having wx notifications nicely
integrated into the desktop just as users expect notifications, I hope Debian
goes for the user-friendly way ;-)


More information about the Freewx-maint mailing list