From 07be2453e059c1cf0a5a2f8f7883e7de84411e97 Mon Sep 17 00:00:00 2001 From: Matthew Barnes Date: Sun, 5 Aug 2012 20:59:18 -0400 Subject: 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 --- plugins/publish-calendar/publish-calendar.c | 2 -- 1 file changed, 2 deletions(-) (limited to 'plugins/publish-calendar') diff --git a/plugins/publish-calendar/publish-calendar.c b/plugins/publish-calendar/publish-calendar.c index 681b1fbe7a..30f376036f 100644 --- a/plugins/publish-calendar/publish-calendar.c +++ b/plugins/publish-calendar/publish-calendar.c @@ -377,7 +377,6 @@ ask_question (GMountOperation *op, primary = g_strndup (message, strlen (message) - strlen (primary)); } - gdk_threads_enter (); dialog = gtk_message_dialog_new (NULL, 0, GTK_MESSAGE_QUESTION, GTK_BUTTONS_NONE, "%s", primary); @@ -409,7 +408,6 @@ ask_question (GMountOperation *op, } gtk_widget_destroy (GTK_WIDGET (dialog)); - gdk_threads_leave (); } static void -- cgit v1.2.3