From 8f55b2775a779489c9747354db00a5eb19568359 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Wed, 1 Aug 2012 10:26:17 +0200 Subject: [PATCH] Expand the thread deprecation documentation The story is slightly different for applications vs libraries; make it clear that libraries should continue using the lock so we don't break applications that haven't been ported to the 'single thread' model yet. --- gdk/gdk.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gdk/gdk.c b/gdk/gdk.c index 752625e55a..6c354b14cc 100644 --- a/gdk/gdk.c +++ b/gdk/gdk.c @@ -661,7 +661,9 @@ gdk_init (int *argc, char ***argv) * it is recommended to use g_idle_add(), g_main_context_invoke() * and similar functions to make these calls from the main thread * instead. The main thread is the thread which has called gtk_init() - * and is running the GTK+ mainloop. + * and is running the GTK+ mainloop. GTK+ itself will continue to + * use the GDK lock internally as long as the deprecated functionality + * is still available, and other libraries should probably do the same. */