summaryrefslogtreecommitdiff
path: root/demos/gtk-demo/images.c
diff options
context:
space:
mode:
authorEmmanuele Bassi <ebassi@gnome.org>2018-02-02 15:51:47 +0100
committerEmmanuele Bassi <ebassi@gnome.org>2018-02-03 12:06:58 +0100
commitc655759cefa56efdb0cb943bb5dada3ff75a963c (patch)
treeef945ea7131b6419d00828fa8661d86691563d83 /demos/gtk-demo/images.c
parent334acbfc39cc08869932ec046e4d13e6c4b64be6 (diff)
downloadgtk+-c655759cefa56efdb0cb943bb5dada3ff75a963c.tar.gz
Replace gdk_threads_add_timeout* with g_timeout_add()
The main GDK thread lock is not portable and deprecated. The only reason why gdk_threads_add_timeout() and gdk_threads_add_timeout_full() exist is to allow invoking a callback with the GDK lock held, in case 3rd party libraries still use the deprecated gdk_threads_enter()/gdk_threads_leave() API. Since we're removing the GDK lock, and we're releasing a new major API, such code cannot exist any more; this means we can use the GLib API for installing timeout callbacks. https://bugzilla.gnome.org/show_bug.cgi?id=793124
Diffstat (limited to 'demos/gtk-demo/images.c')
-rw-r--r--demos/gtk-demo/images.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/demos/gtk-demo/images.c b/demos/gtk-demo/images.c
index b6393cf34a..c3f0f675f6 100644
--- a/demos/gtk-demo/images.c
+++ b/demos/gtk-demo/images.c
@@ -261,9 +261,7 @@ start_progressive_loading (GtkWidget *image)
* The timeout simply simulates a slow data source by inserting
* pauses in the reading process.
*/
- load_timeout = gdk_threads_add_timeout (150,
- progressive_timeout,
- image);
+ load_timeout = g_timeout_add (150, progressive_timeout, image);
g_source_set_name_by_id (load_timeout, "[gtk+] progressive_timeout");
}