]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/html/faqgtk.htm
fixed paper size calculation (convert from 10ths of mm to mm correctly)
[wxWidgets.git] / docs / html / faqgtk.htm
... / ...
CommitLineData
1<HTML>
2
3<HEAD>
4<TITLE>wxWindows 2 for GTK FAQ</TITLE>
5</HEAD>
6
7<BODY BGCOLOR=#FFFFFF TEXT=#000000 LINK=#FF0000 VLINK=#000000>
8
9<font face="Arial, Lucida Sans, Helvetica">
10
11<table width=100% border=0 cellpadding=5 cellspacing=0>
12<tr>
13<td bgcolor="#C4ECF9">
14<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#000000">
15wxWindows 2 for GTK FAQ
16</font>
17</td>
18</tr>
19</table>
20
21<P>
22
23See also <a href="faq.htm">top-level FAQ page</a>.
24<hr>
25<h3>List of questions in this category</h3>
26<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
27<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
28<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
29<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
30<hr>
31
32wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
33which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
34often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>.
35<P>
36
37<h3><a name="gnome">Does wxGTK have GNOME support?</a></h3>
38
39Currently wxGTK does not have any features that would involve dependence on any desktop
40environment&#39;s libraries, so it can work on GNOME, KDE and with other window managers
41without installation hassles. Some GNOME and KDE integration features are file based, and
42so may be added without dependence on libraries. Other features may be supported in the
43future, probably as a separate library.
44<P>
45
46<h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3>
47
48It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
49which causes some trouble with wxWindows&#39; socket code. Common symptoms are that when
50a client tries to establish a connection to an existing server which refuses the request,
51the client will get notified twice, first getting a LOST event and then a CONNECT event.
52This problem can be solved by updating GTK with an official distribution of the library.
53<P>
54
55
56</font>
57
58</BODY>
59
60</HTML>