diff options
author | Matthias Clasen <mclasen@redhat.com> | 2012-08-01 10:26:17 +0200 |
---|---|---|
committer | Matthias Clasen <mclasen@redhat.com> | 2012-08-01 10:26:17 +0200 |
commit | 8f55b2775a779489c9747354db00a5eb19568359 (patch) | |
tree | 329ab287f5099da18da9167f43b2e3d0747f1acb /gdk/gdk.c | |
parent | 3941a8079833fa3d88a68447124eadb8c4c3dfc4 (diff) | |
download | gtk+-8f55b2775a779489c9747354db00a5eb19568359.tar.gz |
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.
Diffstat (limited to 'gdk/gdk.c')
-rw-r--r-- | gdk/gdk.c | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -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. */ |