notify-osd changes the way it supports int32-hints

Bug #390670 reported by Ken VanDine
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Fix Released
Low
Mirco Müller

Bug Description

Binary package hint: gnome-settings-daemon

The way notify-osd treats int32-hints passed to it has changed. The net result of this is that the UI-behaviour of the
feedback-notifications (Volume Up/Down, Screen-Brightness Up/Down, Keyboard-Brightness Up/Down) works now correctly with under- and overshoot throbbing.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Patch from Mirco Müller

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Patch from Mirco Müller

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks but as said on IRC I'm not convinced by the new gboolean use, why the volume value couldn't be used directly?

Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Ken VanDine (ken-vandine) wrote :

Mirco can you respond to Sebastien's comment?

Changed in gnome-settings-daemon (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → Ken VanDine (ken-vandine)
assignee: Ken VanDine (ken-vandine) → Mirco Müller (macslow)
Revision history for this message
Mirco Müller (macslow) wrote :

The design team wants the indicator to "throb" when the user hits volume/brightness up (down) but the systems state-value for that is already at its maximum (minimum). The only way to communicate this to notify-osd by using these special values 101 (-1), because notify-osd has no (and should not have) any knowledge about system state-values for volume/brightness. notify-osd just displays values without any knowledge of its context.

Using values 0 and 100 like it was before, does not work. This is also a bug reported by one of the members of the design team here: https://bugs.edge.launchpad.net/notify-osd/+bug/337820. The cause for that bug is due to the incomplete or wrong patch work done on g-s-d and g-p-m during the jaunty cycle. My patches fixes all that. Initially I also considered fixing this already for the jaunty SRU-phase, but that would have not gone past the SRU-policy-enforcers.

BTW the volume/brightness value is used directly if 0 <= value <= 100.

In addition to that the use of those two booleans make the code/patch easier to read and thus understand.

Revision history for this message
Sebastien Bacher (seb128) wrote :

let's upload this version for now that doesn't seem the optimal way to do things but if that's working

Changed in gnome-settings-daemon (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-settings-daemon - 2.27.3-0ubuntu2

---------------
gnome-settings-daemon (2.27.3-0ubuntu2) karmic; urgency=low

  * debian/patches/16_use_synchronous_notifications.patch:
    - update by Mirco Müller to work better with notify-osd (lp: #390670)

 -- Sebastien Bacher <email address hidden> Tue, 23 Jun 2009 00:07:34 +0200

Changed in gnome-settings-daemon (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.