diff options
| author | Lars Uebernickel <lars.uebernickel@canonical.com> | 2013-09-25 00:11:13 +0200 |
|---|---|---|
| committer | Lars Uebernickel <lars.uebernickel@canonical.com> | 2013-09-25 00:11:13 +0200 |
| commit | ed88015daceb5c5b7972e2d8b94944af182cf3a3 (patch) | |
| tree | 660bd4a015023bcbaf4af8d129e4bbb71ce51c3d /src/idotimestampmenuitem.c | |
| parent | 4bc9bfd877b5c68549aec6b8917edee230f74142 (diff) | |
| download | ayatana-ido-ed88015daceb5c5b7972e2d8b94944af182cf3a3.tar.gz ayatana-ido-ed88015daceb5c5b7972e2d8b94944af182cf3a3.tar.bz2 ayatana-ido-ed88015daceb5c5b7972e2d8b94944af182cf3a3.zip | |
idoscalemenuitem: don't update the action state when the action state changes
GtkRange has the same weird semantics for its "value-changed" signal that the
check menu items have: it is emitted not only on user interaction, but also
when gtk_range_set_value() is called.
The handler to "value-changed" updates the action. gtk_range_set_value() is
called when the action notifies about a state change. Loop, meet loop.
This patch works around that by adding a "value-changed" to IdoScaleMenuItem
that is only emitted when the user changes the slider's value.
Diffstat (limited to 'src/idotimestampmenuitem.c')
0 files changed, 0 insertions, 0 deletions