X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2b5f62a0b2db198609b45dec622a018dae37008e..9c112555198f51fcec71106530cddba95a17f3dc:/docs/html/faqgtk.htm?ds=inline diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm index df33965ef4..6db64c46cb 100644 --- a/docs/html/faqgtk.htm +++ b/docs/html/faqgtk.htm @@ -1,8 +1,7 @@ - -wxWindows 2 for GTK FAQ +wxWidgets 2 for GTK FAQ @@ -13,7 +12,7 @@ -wxWindows 2 for GTK FAQ +wxWidgets 2 for GTK FAQ @@ -21,33 +20,35 @@

-See also top-level FAQ page. +See also top-level FAQ page +and Unix FAQ page.

List of questions in this category

-

What is wxWindows 2 for GTK?

+

What is wxWidgets 2 for GTK?

-wxWindows 2 for GTK is a port of wxWindows to the GTK+ toolkit, -which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is +wxWidgets 2 for GTK is a port of wxWidgets to the GTK+ toolkit, +which is freely available for most flavours of Unix with X. wxWidgets 2 for GTK is often abbreviated to wxGTK. wxGTK has a separate home page here.

-

Why doesn't reading floating point numbers work when using wxWindows?

+

Why doesn't reading floating point numbers work when using wxWidgets?

If your program reads the floating point numbers in the format 123.45 -from a file, it may suddently start returning just 123 instead of the +from a file, it may suddenly start returning just 123 instead of the correct value on some systems -- which is all the more mysterious as the same code in a standalone program works just fine. @@ -74,7 +75,7 @@ future, probably as a separate library.

Warning about GTK+ libraries supplied with RedHat

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 +which causes some trouble with wxWidgets' 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. @@ -84,13 +85,13 @@ This problem can be solved by updating GTK with an official distribution of the Robert Roebling replies:

-"The important thing is the libc version that your app +"The important thing is the libc version that your app is linked against. The most recent version is 2.2.5 and programs linked against it will not run with version 2.1.X so that you will fare best if you compile your app on a 2.1.X system. It will then run on practically all Linux distros (if you link you app statically against -the image libraries and std C++ lib)." +the image libraries and std C++ lib)."

Can I statically link the GTK+ library?

@@ -99,7 +100,7 @@ No, this is not possible. It leads to crashes in GTK+.

Why does my simple program using -EVT_CHAR doesn't work?

+EVT_CHAR not work? In wxGTK, the frames never get focus and so can never receive CHAR nor KEY events so an EVT_CHAR handler for a frame will be @@ -109,6 +110,14 @@ frame.

+

How do I trace the cause of an X11 error such as BadMatch?

+ +When a fatal X11 error occurs, the application quits with no stack trace. +To find out where the problem is, put a breakpoint on g_log (b g_log +in gdb). + +

+