Added window styles to wxToolBar handler.

[wxWidgets.git] / utils / configtool / docs / manual / configtool.tex

diff --git a/utils/configtool/docs/manual/configtool.tex b/utils/configtool/docs/manual/configtool.tex
index 5c513ef2e16785147aaec191ea1c47b20b5a8999..b0cf64994cb9df8a0499d0a6b2920040911b645c 100644 (file)
--- a/utils/configtool/docs/manual/configtool.tex
+++ b/utils/configtool/docs/manual/configtool.tex
@@ -151,6 +151,15 @@ the licence files in the installation directory:
 
 \section{What's New?}\label{whatsnew}
 
+{\bf Version 1.02, June 16th 2003}
+
+\begin{itemize}\itemsep=10pt
+\item The <b>Platform</b> group has been renamed
+<b>Target</b>, since there can be multiple targets
+per platform.
+\item The Windows/Universal target has been added.
+\end{itemize}
+
 {\bf Version 1.01, June 14th 2003}
 
 \begin{itemize}\itemsep=10pt
@@ -377,6 +386,8 @@ with files.
 \twocolitem{{\bf Save Setup.h...} (Ctrl+H)}{Saves the generated setup.h file in the specified location.}
 \twocolitem{{\bf Save Configure Script...} (Ctrl+G)}{Saves the generated script containing a configure command in the specified location.}
 \twocolitem{\hrule}{\htmlonly{\hrule}}
+\twocolitem{{\bf Go} (F5)}{Saves the generated setup.h file or configurewx.sh script (according to the default setting) in the last-saved.}
+\twocolitem{\hrule}{\htmlonly{\hrule}}
 \twocolitem{{\bf Exit} (Alt+F4)}{Exits the program.}
 \end{twocollist}
 
@@ -485,6 +496,8 @@ commands.
 \twocolitem{\image{}{cut.png}{\bf  Cut}}{Cuts the selected option and copies it to the internal clipboard..}
 \twocolitem{\image{}{paste.png}{\bf  Paste}}{Pastes the option from the clipboard to the configuration tree.}
 \twocolitem{\hrule}{\htmlonly{\hrule}}
+\twocolitem{\image{}{go.png}{\bf Go}}{Saves the generated setup.h file or configurewx.sh script (according to the default setting) in the last-saved.}
+\twocolitem{\hrule}{\htmlonly{\hrule}}
 \twocolitem{\image{}{help.png}{\bf  Help}}{Shows the wxWindows manual topic for the
 \twocolitem{\image{}{helpcs.png}{\bf  Context Help}}{Shows a context-sensitive help
 cursor; click on a window to show brief help about that window.}
@@ -594,7 +607,12 @@ group and its children is considered to be a virtual
 taken into account if the option is a radio option
 or group. For each radio option, all other mutually
 exclusive options need to be listed. See the
-{\bf Platform} group for an example of this.
+{\bf Target} group for an example of this.
+
+The results of these dependencies can be overridden by
+indeterminate-if, which is done last of all and can
+make the option user-selectable when otherwise it
+would be constrained to be enabled or disabled.
 
 \section{How \ctshortname generates the configure commands}
 
@@ -623,7 +641,7 @@ by using the {\bf value} custom string property.
 
 \section{How \ctshortname generates the setup.h file}
 
-The {\bf Platforms} group is ignored. In all other
+The {\bf Target} group is ignored. In all other
 cases, if the setting is prefixed by wxUSE_...
 and it's a boolean setting, \ctshortname will
 output 1 or 0 depending on the setting state.
@@ -648,8 +666,8 @@ if the option is constrained to always be disabled
 or enabled in the current context, then it is greyed out
 (deactivated) to prevent the user from changing the state.
 
-There are four kinds of dependencies: requires, precludes,
-enabled-if, and enabled-if-not. Each one represents a
+There are five kinds of dependencies: requires, precludes,
+enabled-if, enabled-if-not, and indeterminate-if. Each one represents a
 relationship between the current option (a) and one
 or more named options (b). For the sake of argument
 we will consider only one other option, but multiple
@@ -706,6 +724,24 @@ For example, wxUSE_TOOLBAR_SIMPLE enabled-if-not wxUSE_TOOLBAR_NATIVE.
     1        1
 \end{verbatim}
 
+5. a {\bf indeterminate-if} b
+
+For example, wxUSE_UNICODE indeterminate-if Custom.
+
+\begin{verbatim}
+    a        b
+
+    ?        1
+\end{verbatim}
+
+This overrides all the other dependencies, and allows you
+to make an option user-choosable in some circumstances,
+when otherwise it would be constrained to be either enabled or
+disabled. You may need to use an intermediate option to
+make sensible use of this: for example make the intermediate
+option dependent on a number of factors, such as Unicode not being
+available on some platforms.
+
 \section{How to specify platform-specific dependencies}\label{platformdependencies}
 
 You can associate one or more options as part of the