Commit f3e4d4f0 authored by Matthias Clasen's avatar Matthias Clasen

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)
parent c7eb1aaf
2002-11-26 Matthias Clasen <maclas@gmx.de>
* 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 <maclas@gmx.de>
* gdk/tmpl/x_interaction.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.
</para>
<para>
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.)
</para>
<para>A minimal main program for a threaded GTK+ application
looks like:</para>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment