Various underscore doc fixes

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@31776 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Ryan Norton
2005-02-06 02:47:31 +00:00
parent 14ca93a0d9
commit bb772a8edf
6 changed files with 22 additions and 22 deletions

View File

@@ -683,7 +683,7 @@ enum wxKillError
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}
@@ -2829,10 +2829,10 @@ Gets the currently active window (Windows only).
\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}
@@ -2855,9 +2855,9 @@ Under X only, returns the current display name. See also \helpref{wxSetDisplayNa
\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}

View File

@@ -9,7 +9,7 @@ identify the selection, or to change the menu item in some way. A menu item
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

View File

@@ -188,7 +188,7 @@ under both Unix and Windows but all the other signals are equivalent to
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:

View File

@@ -6,7 +6,7 @@ When there aren't interface guidelines defined for a particular platform or tool
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}
@@ -33,14 +33,14 @@ Constructor for a wxStdDialogButtonSizer.
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}

View File

@@ -215,7 +215,7 @@ sizer->Add(win);
- 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*().

View File

@@ -920,8 +920,8 @@ and OS on which the program will be compiled/run is Unicode capable.
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}