The {\it flags} parameter can be wxKILL\_NOCHILDREN (the default),
or wxKILL\_CHILDREN, in which case the child processes of this
process will be killed too. Note that under Unix, for wxKILL\_CHILDREN
-to work you should have created the process by passing wxEXEC\_MAKE_GROUP\_LEADER
+to work you should have created the process by passing wxEXEC\_MAKE\_GROUP\_LEADER
to wxExecute.
\wxheading{See also}
\func{wxBatteryState}{wxGetBatteryState}{\void}
-Returns battery state as one of \texttt{wxBATTERY_NORMAL_STATE},
-\texttt{wxBATTERY_LOW_STATE}, \texttt{wxBATTERY_CRITICAL_STATE},
-\texttt{wxBATTERY_SHUTDOWN_STATE} or \texttt{wxBATTERY_UNKNOWN_STATE}.
-\texttt{wxBATTERY_UNKNOWN_STATE} is also the default on platforms where
+Returns battery state as one of \texttt{wxBATTERY\_NORMAL\_STATE},
+\texttt{wxBATTERY\_LOW\_STATE}, \texttt{wxBATTERY\_CRITICAL\_STATE},
+\texttt{wxBATTERY\_SHUTDOWN\_STATE} or \texttt{wxBATTERY\_UNKNOWN\_STATE}.
+\texttt{wxBATTERY\_UNKNOWN\_STATE} is also the default on platforms where
this feature is not implemented.
\wxheading{Include files}
\func{wxPowerType}{wxGetPowerType}{\void}
-Returns the type of power source as one of \texttt{wxPOWER_SOCKET},
-\texttt{wxPOWER_BATTERY} or \texttt{wxPOWER_UNKNOWN}.
-\texttt{wxPOWER_UNKNOWN} is also the default on platforms where this
+Returns the type of power source as one of \texttt{wxPOWER\_SOCKET},
+\texttt{wxPOWER\_BATTERY} or \texttt{wxPOWER\_UNKNOWN}.
+\texttt{wxPOWER\_UNKNOWN} is also the default on platforms where this
feature is not implemented.
\wxheading{Include files}
with a special identifier $-1$ is a separator item and doesn't have an
associated command but just makes a separator line appear in the menu.
-{\bf NB:} Please note that {\it wxID_ABOUT} and {\it wxID_EXIT} are
+{\bf NB:} Please note that {\it wxID\_ABOUT} and {\it wxID\_EXIT} are
predefined by wxWidgets and have a special meaning since entries
using these IDs will be taken out of the normal menus under MacOS X
and will be inserted into the system menu (following the appropriate
The {\it flags} parameter can be wxKILL\_NOCHILDREN (the default),
or wxKILL\_CHILDREN, in which case the child processes of this
process will be killed too. Note that under Unix, for wxKILL\_CHILDREN
-to work you should have created the process passing wxEXEC\_MAKE_GROUP\_LEADER.
+to work you should have created the process passing wxEXEC\_MAKE\_GROUP\_LEADER.
Returns the element of {\tt wxKillError} enum:
TO USE THIS CLASS: First, add buttons to the sizer by calling AddButton (or SetAffirmativeButton, SetNegativeButton, or SetCancelButton) and then call Finalise in order to create the actual button layout used. Other than these special operations, this sizer works like any other sizer.
-ALSO NOTE: If you add a button with wxID_SAVE, on Mac OS X the button will be renamed to "Save" and the wxID_NO button will be renamed to "Don't Save" in accordance with the Mac OS X Human Interface Guidelines.
+ALSO NOTE: If you add a button with wxID\_SAVE, on Mac OS X the button will be renamed to "Save" and the wxID\_NO button will be renamed to "Don't Save" in accordance with the Mac OS X Human Interface Guidelines.
\wxheading{Derived from}
Adds a button to the wxStdDialogButtonSizer. The button must have one of the following IDs:
\begin{itemize}
- \item wxID_OK
- \item wxID_YES
- \item wxID_SAVE
- \item wxID_APPLY
- \item wxID_NO
- \item wxID_CANCEL
- \item wxID_HELP
- \item wxID_CONTEXT_HELP
+ \item wxID\_OK
+ \item wxID\_YES
+ \item wxID\_SAVE
+ \item wxID\_APPLY
+ \item wxID\_NO
+ \item wxID\_CANCEL
+ \item wxID\_HELP
+ \item wxID\_CONTEXT\_HELP
\end{itemize}
\membersection{wxStdDialogButtonSizer::Finalise}\label{wxstddialogbuttonsizerfinalise}
- wxSizer::Add/Insert returns pointer to wxSizerItem just added so conditions
writeen with if(Add(..)==true) will not work. Use if(Add(..)) instead.
-- New \helpref{wxBrush::IsHatch()}{wxbrushishatch} checking for brush type replaces IS_HATCH macro.
+- New \helpref{wxBrush::IsHatch()}{wxbrushishatch} checking for brush type replaces IS\_HATCH macro.
- wxSystemSettings::GetSystem*() members deprecated and replaced with wxSystemSettings::Get*().
The one major difference in writing code that can be compiled in either
unicode or non-unicode builds that is specific to the wxODBC classes is to
-use the SQL_C_WXCHAR datatype for string columns rather than SQL_C_CHAR or
-SQL_C_WCHAR.
+use the SQL\_C\_WXCHAR datatype for string columns rather than SQL\_C\_CHAR or
+SQL\_C\_WCHAR.
\subsection{wxODBC - Sample Code}\label{wxodbcsamplecode1}