callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add hint about calling gdk_flush() before gdk_threads_leave(). (#70665,

Browse Source 
* gdk/tmpl/threads.sgml: Add hint about calling gdk_flush() before
	gdk_threads_leave().  (#70665, wording suggested by Owen Taylor)
This commit is contained in:
Matthias Clasen
2002-11-26 01:29:05 +00:00
parent c7eb1aaf55
commit f3e4d4f0fa
2 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/ChangeLog
View File

@ -1,3 +1,8 @@
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> 2002-11-23 Matthias Clasen <maclas@gmx.de>
* gdk/tmpl/x_interaction.sgml: * gdk/tmpl/x_interaction.sgml:

10
docs/reference/gdk/tmpl/threads.sgml
View File

@ -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. a signal handler with a gdk_threads_enter()/gdk_threads_leave() pair.
</para> </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 <para>A minimal main program for a threaded GTK+ application
looks like:</para> looks like:</para>