diff options
| author | Matthias Clasen <mclasen@redhat.com> | 2015-01-09 21:13:10 -0500 |
|---|---|---|
| committer | Matthias Clasen <mclasen@redhat.com> | 2015-01-09 21:15:07 -0500 |
| commit | 9fcbae2d857ed35483700be13d62a3590c719ee8 (patch) | |
| tree | 0a2116dcdecfc3df9b771cf46dd2a2af3f60b454 | |
| parent | 206f0bbf7f259868cd434733fd258810fad12281 (diff) | |
| download | gtk+-9fcbae2d857ed35483700be13d62a3590c719ee8.tar.gz | |
GtkScrolledWindow: Don't start fading right away
When we get a leave event, we need to remove the over bit,
since we may not get motion events that tell us when we lose
proximity, but we don't have to fade out right away - that
will happen on its on due to inactivity a bit later. Having
the indicator stay visible for a bit feels more relaxed.
| -rw-r--r-- | gtk/gtkscrolledwindow.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/gtk/gtkscrolledwindow.c b/gtk/gtkscrolledwindow.c index 174f70938d..e1128e0340 100644 --- a/gtk/gtkscrolledwindow.c +++ b/gtk/gtkscrolledwindow.c @@ -394,9 +394,7 @@ gtk_scrolled_window_leave_notify (GtkWidget *widget, if (priv->use_indicators) { indicator_set_over (&priv->hindicator, FALSE); - indicator_start_fade (&priv->hindicator, 0.0); indicator_set_over (&priv->vindicator, FALSE); - indicator_start_fade (&priv->vindicator, 0.0); } return GDK_EVENT_PROPAGATE; |