From f3e4d4f0fa96b02a6adf545e0f644dd70f1ba897 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Tue, 26 Nov 2002 01:29:05 +0000 Subject: [PATCH] Add hint about calling gdk_flush() before gdk_threads_leave(). (#70665, * gdk/tmpl/threads.sgml: Add hint about calling gdk_flush() before gdk_threads_leave(). (#70665, wording suggested by Owen Taylor) --- docs/reference/ChangeLog | 5 +++++ docs/reference/gdk/tmpl/threads.sgml | 10 ++++++++++ 2 files changed, 15 insertions(+) diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog index a2617149ed..4bb0cf1394 100644 --- a/docs/reference/ChangeLog +++ b/docs/reference/ChangeLog @@ -1,3 +1,8 @@ +2002-11-26 Matthias Clasen + + * gdk/tmpl/threads.sgml: Add hint about calling gdk_flush() before + gdk_threads_leave(). (#70665, wording suggested by Owen Taylor) + 2002-11-23 Matthias Clasen * gdk/tmpl/x_interaction.sgml: diff --git a/docs/reference/gdk/tmpl/threads.sgml b/docs/reference/gdk/tmpl/threads.sgml index a30e7b2bea..c4f8d69eea 100644 --- a/docs/reference/gdk/tmpl/threads.sgml +++ b/docs/reference/gdk/tmpl/threads.sgml @@ -43,6 +43,16 @@ As always, you must also surround any calls to GTK+ not made within a signal handler with a gdk_threads_enter()/gdk_threads_leave() pair. + +Before calling gdk_threads_leave() from a thread other +than your main thread, you probably want to call gdk_flush() +to send all pending commands to the windowing system. +(The reason you don't need to do this from the main thread +is that GDK always automatically flushes pending commands +when it runs out of incoming events to process and has +to sleep while waiting for more events.) + + A minimal main program for a threaded GTK+ application looks like: