[gtk+/gtk-2-22] Don't use g_idle_add to schedule idles in GDK



commit 9190497b4a8eef15375b1b7473ca9cd87bc612a5
Author: Matthias Clasen <mclasen redhat com>
Date:   Fri Sep 10 22:35:36 2010 -0400

    Don't use g_idle_add to schedule idles in GDK
    
    We need to use gdk_threads_add_idle, in order to keep GDK code
    under the GDK lock.
    
    Bug 629277
    (cherry picked from commit 08dd02fe255487f5c7953de9b2c8b63c2e937989)

 gdk/gdkwindow.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/gdk/gdkwindow.c b/gdk/gdkwindow.c
index c3dd544..74e0bd0 100644
--- a/gdk/gdkwindow.c
+++ b/gdk/gdkwindow.c
@@ -10427,10 +10427,10 @@ _gdk_synthesize_crossing_events_for_geometry_change (GdkWindow *changed_window)
       !toplevel_priv->synthesize_crossing_event_queued)
     {
       toplevel_priv->synthesize_crossing_event_queued = TRUE;
-      g_idle_add_full (GDK_PRIORITY_EVENTS - 1,
-		       do_synthesize_crossing_event,
-		       g_object_ref (toplevel),
-		       g_object_unref);
+      gdk_threads_add_idle_full (GDK_PRIORITY_EVENTS - 1,
+                                 do_synthesize_crossing_event,
+                                 g_object_ref (toplevel),
+                                 g_object_unref);
     }
 }
 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]