See also <a href="faq.htm">top-level FAQ page</a>.
<hr>
-
-<h3>What is wxWindows 2 for GTK?</h3>
+<h3>List of questions in this category</h3>
+<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
+<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
+<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
+<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
+<hr>
wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>.
<P>
-<h3>Does wxGTK have GNOME support?</h3>
+<h3><a name="gnome">Does wxGTK have GNOME support?</a></h3>
Currently wxGTK does not have any features that would involve dependence on any desktop
-environment's libraries, so it can work on GNOME, KDE and with other window managers
+environment's libraries, so it can work on GNOME, KDE and with other window managers
without installation hassles. Some GNOME and KDE integration features are file based, and
so may be added without dependence on libraries. Other features may be supported in the
future, probably as a separate library.
<P>
+<h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3>
+
+It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
+which causes some trouble with wxWindows' socket code. Common symptoms are that when
+a client tries to establish a connection to an existing server which refuses the request,
+the client will get notified twice, first getting a LOST event and then a CONNECT event.
+This problem can be solved by updating GTK with an official distribution of the library.
+<P>
+
</font>
projects / wxWidgets.git / blobdiff