Comment 9 for bug 428509

Am Freitag, den 02.10.2009, 17:00 +0000 schrieb Mark Shuttleworth:

> Mirco, did we ever run notify-osd in a mode where it displayed
> notification urgency (critical, normal, low)? I wonder if we shouldn't
> take the view that full-screen apps block non-critical async
> notifications, and that some system-wide async notifications like
> network loss would be classed as critical.

 This very capability is implemented in notify-osd coming with Karmic.
During "fullscreen apps" (in other words when in "screensaver
inhibited"-mode, e.g. by running totem or OO-Impress in
presentation-mode) only synchronous and critical asynchronous
notifications are displayed. Asynchronous notifications with low- and
normal urgency are suppressed in this "screensaver inhibited"-mode.

 If you want to test that yourself, there are three asynchronous
notification examples (with low, normal and critical urgency) in
notify-osd's source tree. To get and try them do:

        bzr branch lp:notify-osd
        cd notify-osd/examples
        ./low-urgency.py
        ./normal-urgency.py
        ./urgent-urgency.py

 To make notify-osd display a notifications urgency within each bubble
do:

        killall -15 notify-osd
        DEBUG=1 /usr/lib/notify-osd/notify-osd

Best regards ...

Mirco