Doc fixes

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@32252 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

docs/latex/wx/radiobut.tex

@@ -3,6 +3,9 @@
 A radio button item is a button which usually denotes one of several mutually
 exclusive options. It has a text label next to a (usually) round button.
 
+You can create a group of mutually-exclusive radio buttons by specifying {\tt wxRB\_GROUP} for
+the first in the group. The group ends when another radio button group is created, or there are no more radio buttons.
+
 \wxheading{Derived from}
 
 \helpref{wxControl}{wxcontrol}\\
@@ -19,11 +22,11 @@ exclusive options. It has a text label next to a (usually) round button.
 \twocolwidtha{5cm}
 \begin{twocollist}\itemsep=0pt
 \twocolitem{\windowstyle{wxRB\_GROUP}}{Marks the beginning of a new group of radio buttons.}
-\twocolitem{\windowstyle{wxRB\_SINGLE}}{If your radio buttons are not
-consecutive siblings, they cannot form a group under Windows and you should use
-this style to indicate that each of them is handled individually.}
-\twocolitem{\windowstyle{wxRB\_USE\_CHECKBOX}}{Use of the checkbox control instead of radio
-button (currently supported only on PalmOS)}
+\twocolitem{\windowstyle{wxRB\_SINGLE}}{In some circumstances, radio buttons that are not
+consecutive siblings trigger a hang bug in Windows (only). If this happens, add this style
+to mark the button as not belonging to a group, and implement the mutually-exclusive group behaviour yourself.}
+\twocolitem{\windowstyle{wxRB\_USE\_CHECKBOX}}{Use a checkbox button instead of radio
+button (currently supported only on PalmOS).}
 \end{twocollist}
 
 See also \helpref{window styles overview}{windowstyles}.

docs/latex/wx/settings.tex

@@ -155,3 +155,18 @@ where it would otherwise present the information only in audible form; zero othe
 \pythonnote{This static method is implemented in Python as a
 standalone function named {\tt wxSystemSettings\_GetMetric}}
 
+\membersection{wxSystemSettings::GetScreenType}\label{wxsystemsettingsgetscreentype}
+
+\func{static wxSystemScreenType}{GetScreenType}{\void}
+
+Returns the screen type. The return value is one of:
+
+\twocolwidtha{7cm}
+\begin{twocollist}\itemsep=0pt
+\twocolitem{{\bf wxSYS_SCREEN\_NONE}}{Undefined screen type}
+\twocolitem{{\bf wxSYS_SCREEN\_TINY}}{Tiny screen, less than 320x240}
+\twocolitem{{\bf wxSYS_SCREEN\_PDA}}{PDA screen, 320x240 or more but less than 640x480}
+\twocolitem{{\bf wxSYS_SCREEN\_SMALL}}{Small screen, 640x480 or more but less than 800x600}
+\twocolitem{{\bf wxSYS_SCREEN\_DESKTOP}}{Desktop screen, 800x600 or more}
+\end{twocollist}
+

docs/latex/wx/txrc.tex

@@ -54,7 +54,7 @@ To create an XRC file, you can use one of the following methods.
 \item use \urlref{XRCed}{http://xrced.sf.net}, a wxPython-based
 dialog editor that you can find in the {\tt wxPython/tools} subdirectory of the wxWidgets
 CVS archive;
-\item use \urlref{Glade}{http://wxglade.sf.net}, a GUI designer written in wxPython. At the moment it can generate Python, C++ and XRC;
+\item use \urlref{wxGlade}{http://wxglade.sf.net}, a GUI designer written in wxPython. At the moment it can generate Python, C++ and XRC;
 \item convert WIN32 RC files to XRC with the tool in {\tt contrib/utils/convertrc}.
 \end{itemize}
 
@@ -80,7 +80,7 @@ To compile binary resource files, use the command-line wxrc utility. It takes on
 \item -e (--extra-cpp-code): if used together with -c, generates C++ header file
 containing class definitions for the windows defined by the XRC file (see special subsection) 
 \item -u (--uncompressed): do not compress XML files (C++ only)
-\item -g (--gettext): output .po catalog (to stdout, or a file if -o is used)
+\item -g (--gettext): output underscore-wrapped strings that poEdit or gettext can scan. Outputs to stdout, or a file if -o is used
 \item -n (--function) <name>: specify C++ function name (use with -c)
 \item -o (--output) <filename>: specify the output file, such as resource.xrs or resource.cpp
 \item -l (--list-of-handlers) <filename>: output a list of necessary handlers to this file