summaryrefslogtreecommitdiff
path: root/doc/hackersguide
diff options
context:
space:
mode:
authorMichael Roitzsch <mroi@users.sourceforge.net>2004-06-27 11:16:20 +0000
committerMichael Roitzsch <mroi@users.sourceforge.net>2004-06-27 11:16:20 +0000
commit29f04d913513a470bc91aff3e6c0fca699e460f8 (patch)
treef98c80765204e178ac1742f86c554f12822a4e57 /doc/hackersguide
parent5db55e3f0cf5e541516dc18070a7ac4bb9a2f992 (diff)
downloadxine-lib-29f04d913513a470bc91aff3e6c0fca699e460f8.tar.gz
xine-lib-29f04d913513a470bc91aff3e6c0fca699e460f8.tar.bz2
calling XInitThreads() is definitely the frontend's job, because it has
to call Xlib functions before xine to properly fill x11_visual_t CVS patchset: 6755 CVS date: 2004/06/27 11:16:20
Diffstat (limited to 'doc/hackersguide')
-rw-r--r--doc/hackersguide/library.sgml6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/hackersguide/library.sgml b/doc/hackersguide/library.sgml
index 63e550e3d..907346bc2 100644
--- a/doc/hackersguide/library.sgml
+++ b/doc/hackersguide/library.sgml
@@ -40,6 +40,12 @@
will find a very easy and hopefully self-explaining xine frontend
to give you a start.
</para>
+ <para>
+ One important thing to note is that any X11 based xine-lib frontend
+ must call <function>XInitThreads()</function> before calling the
+ first Xlib function, because xine will access the display from
+ within a different thread than the frontend.
+ </para>
<sect2>
<title>Source code of a simple X11 frontend</title>
<programlisting>