diff options
| author | Matthew Barnes <mbarnes@redhat.com> | 2012-08-06 08:59:18 +0800 |
|---|---|---|
| committer | Matthew Barnes <mbarnes@redhat.com> | 2012-08-06 10:12:26 +0800 |
| commit | 07be2453e059c1cf0a5a2f8f7883e7de84411e97 (patch) | |
| tree | a35669cf5ea51b57da5635b0fdc30ee81f488c5f /calendar/gui/e-day-view.c | |
| parent | 74d33d365d99684b279088f2a24b53896b51f899 (diff) | |
| download | gsoc2013-evolution-07be2453e059c1cf0a5a2f8f7883e7de84411e97.tar.gz gsoc2013-evolution-07be2453e059c1cf0a5a2f8f7883e7de84411e97.tar.zst gsoc2013-evolution-07be2453e059c1cf0a5a2f8f7883e7de84411e97.zip | |
Remove all GDK threads usage.
According to [1], we don't need to worry about GDK's global lock since
we don't call gdk_threads_init() or gdk_threads_set_lock_functions().
The GDK threads API is being aggressively deprecated by GTK+ developers
so let's just abandon it entirely. I've never really understood when
you're supposed to use it or not use it anyway, so it's good to be rid
of this confusion.
[1] https://mail.gnome.org/archives/desktop-devel-list/2012-August/msg00005.html
Diffstat (limited to 'calendar/gui/e-day-view.c')
| -rw-r--r-- | calendar/gui/e-day-view.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/calendar/gui/e-day-view.c b/calendar/gui/e-day-view.c index 620b664f11..c2b7fc78fd 100644 --- a/calendar/gui/e-day-view.c +++ b/calendar/gui/e-day-view.c @@ -7131,11 +7131,8 @@ e_day_view_auto_scroll_handler (gpointer data) day_view = E_DAY_VIEW (data); - GDK_THREADS_ENTER (); - if (day_view->auto_scroll_delay > 0) { day_view->auto_scroll_delay--; - GDK_THREADS_LEAVE (); return TRUE; } @@ -7189,7 +7186,6 @@ e_day_view_auto_scroll_handler (gpointer data) } } - GDK_THREADS_LEAVE (); return TRUE; } |