diff options
author | Emmanuele Bassi <ebassi@gnome.org> | 2018-02-02 15:51:47 +0100 |
---|---|---|
committer | Emmanuele Bassi <ebassi@gnome.org> | 2018-02-03 12:06:58 +0100 |
commit | c655759cefa56efdb0cb943bb5dada3ff75a963c (patch) | |
tree | ef945ea7131b6419d00828fa8661d86691563d83 /gtk/gtkprintoperation.c | |
parent | 334acbfc39cc08869932ec046e4d13e6c4b64be6 (diff) | |
download | gtk+-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 'gtk/gtkprintoperation.c')
-rw-r--r-- | gtk/gtkprintoperation.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gtk/gtkprintoperation.c b/gtk/gtkprintoperation.c index cd2a082af3..68a2e1555c 100644 --- a/gtk/gtkprintoperation.c +++ b/gtk/gtkprintoperation.c @@ -3008,9 +3008,9 @@ print_pages (GtkPrintOperation *op, G_CALLBACK (handle_progress_response), op); priv->show_progress_timeout_id = - gdk_threads_add_timeout (SHOW_PROGRESS_TIME, - (GSourceFunc)show_progress_timeout, - data); + g_timeout_add (SHOW_PROGRESS_TIME, + (GSourceFunc) show_progress_timeout, + data); g_source_set_name_by_id (priv->show_progress_timeout_id, "[gtk+] show_progress_timeout"); data->progress = progress; |