\end{verbatim}
There's another way of taking advantage of this class: you can use it in your code and use
-platform native icons as provided by
-\helpref{wxArtProvider::GetBitmap}{wxartprovidergetbitmap} or
+platform native icons as provided by \helpref{wxArtProvider::GetBitmap}{wxartprovidergetbitmap} or
\helpref{wxArtProvider::GetIcon}{wxartprovidergeticon} (NB: this is not yet really
possible as of wxWidgets 2.3.3, the set of wxArtProvider bitmaps is too
small).
\section{\class{wxCalendarCtrl}}\label{wxcalendarctrl}
-The calendar control allows the user to pick a date interactively. For this,
-it displays a window containing several parts: the control to pick the month
-and the year at the top (either or both of them may be disabled) and a month
+The calendar control allows the user to pick a date. For this,
+it displays a window containing several parts: a control at the top to pick the month
+and the year (either or both of them may be disabled), and a month
area below them which shows all the days in the month. The user can move the
current selection using the keyboard and select the date (generating
{\tt EVT\_CALENDAR} event) by pressing {\tt <Return>} or double clicking it.
\section{\class{wxCmdLineParser}}\label{wxcmdlineparser}
-wxCmdLineParser is a class for parsing command line.
+wxCmdLineParser is a class for parsing the command line.
It has the following features:
\twocolitem{{\bf WriteBool(key, value)}}{Writes a boolean}
\end{twocollist}
}}
+
\section{Preprocesser symbols defined by wxWidgets}\label{cppconst}
-Here is the list of preprocessor symbols used in the wxWidgets source grouped
+These are preprocessor symbols used in the wxWidgets source, grouped
by category (and sorted by alphabetical order inside each category). All of
-these macros except for \texttt{wxUSE\_XXX} variety is defined if the
+these macros except for the \texttt{wxUSE\_XXX} variety is defined if the
corresponding condition is true and undefined if it isn't, so they should be
-always tested usin \texttt{#ifdef} and not \texttt{#if}.
-
+always tested using \texttt{#ifdef} and not \texttt{#if}.
\subsection{GUI system}\label{guisystemconst}
\section{\class{wxDatePickerCtrl}}\label{wxdatepickerctrl}
-This control allows the user to select a date. Unlike
+This control allows the user to select a date. Unlike
\helpref{wxCalendarCtrl}{wxcalendarctrl}, which is a relatively big control,
-it is implemented as a small window showing the currently selected date and
-allowing to edit it directly using the keyboard and may also display a popup
+wxDatePickerCtrl is implemented as a small window showing the currently selected date.
+The control can be edited using the keyboard, and can also display a popup
window for more user-friendly date selection, depending on the styles used and
the platform.
+It is only available if \texttt{wxUSE\_DATEPICKCTRL} is set to $1$.
+
\wxheading{Derived from}
\helpref{wxControl}{wxcontrol}\\
<wx/dateevt.h>
-(only available if \texttt{wxUSE\_DATEPICKCTRL} is set to $1$)
-
\wxheading{Window styles}
\twocolwidtha{5cm}%
Calling this method does not result in a date change event.
-
\section{\class{wxDateEvent}}\label{wxdateevent}
-This event class carries information about a date change and is used together
-with \helpref{wxDatePickerCtrl}{wxdatepickerctrl} and serves as a base class
+This event class holds information about a date change and is used together
+with \helpref{wxDatePickerCtrl}{wxdatepickerctrl}. It also serves as a base class
for \helpref{wxCalendarEvent}{wxcalendarevent}.
\wxheading{Derived from}
<wx/dateevt.h>
-
\latexignore{\rtfignore{\wxheading{Members}}}
\membersection{wxDateEvent::GetDate}\label{wxdateeventgetdate}
Sets the date carried by the event, normally only used by the library
internally.
-
wxWidgets defines a common API across platforms, but uses the native graphical
user interface (GUI) on each platform, so your program will take on the native
-look and feel that users are familiar with. Unfortunatelly native toolkits and
-dedicated hardware not always support complete set of API functionality. This
-chapter collects notes about differences among supported platforms and ports.
+look and feel that users are familiar with. Unfortunately native toolkits and
+hardware do not always support the functionality that the wxWidgets API
+requires. This chapter collects notes about differences among supported platforms and ports.
\input wxgtk.tex
\input wxmsw.tex
First, a brief introduction to wxRenderer and why it is needed.
Usually wxWidgets uses the underlying low level GUI system to draw all the
-controls -- this is what we mean when we say that it is a ``native'' framework.
+controls - this is what we mean when we say that it is a ``native'' framework.
However not all controls exist under all (or even any) platforms and in this
case wxWidgets provides a default, generic, implementation of them written in
wxWidgets itself.
A slider is a control with a handle which can be pulled
back and forth to change the value.
-In Windows versions below Windows 95, a scrollbar is used to simulate the slider. In Windows 95,
-the track bar control is used.
+On Windows, the track bar control is used.
Slider events are handled in the same way as a scrollbar.
\section{\class{wxStackWalker}}\label{wxstackwalker}
-wxStackWalker allows to enumerate, or walk, the stack frames or, in other
-words, the functions callstack. It is mostly useful in only two situations:
+wxStackWalker allows an application to enumerate, or walk, the stack frames (the function callstack).
+It is mostly useful in only two situations:
inside \helpref{wxApp::OnFatalException}{wxapponfatalexception} function to
programmatically get the location of the crash and, in debug builds, in
\helpref{wxApp::OnAssert}{wxapponassert} to report the caller of the failed
assert.
-wxStackWalker works by repeatedly calling
-\helpref{OnStackFrame}{wxstackwalkeronstackframe} method for each frame in the
+wxStackWalker works by repeatedly calling
+the \helpref{OnStackFrame}{wxstackwalkeronstackframe} method for each frame in the
stack, so to use it you must derive your own class from it and override this
method.
\section{\class{wxStdDialogButtonSizer}}\label{wxstddialogbuttonsizer}
-This class creates button layouts which conform to the standard button spacing and ordering defined by the platform or toolkit's user interface guidelines (if such things exist). By using this class, you can ensure that all your standard dialogs look correct on all major platforms. Currently it conforms to the Windows, GTK and Mac OS X human interface guidelines.
+This class creates button layouts which conform to the standard button spacing and ordering defined by the platform
+or toolkit's user interface guidelines (if such things exist). By using this class, you can ensure that all your
+standard dialogs look correct on all major platforms. Currently it conforms to the Windows, GTK+ and Mac OS X
+human interface guidelines.
-When there aren't interface guidelines defined for a particular platform or toolkit, wxStdDialogButtonSizer reverts to the Windows implementation.
+When there aren't interface guidelines defined for a particular platform or toolkit, wxStdDialogButtonSizer reverts
+to the Windows implementation.
-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.
+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.
+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}
\func{void}{AddButton}{\param{wxButton* }{button}}
-Adds a button to the wxStdDialogButtonSizer. The button must have one of the following IDs:
+Adds a button to the wxStdDialogButtonSizer. The button must have one of the following identifiers:
\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}
\func{void}{SetAffirmativeButton}{\param{wxButton* }{button}}
-Sets the affirmative button for the sizer. This allows you to use IDs other than the standard IDs outlined above.
+Sets the affirmative button for the sizer. This allows you to use identifiers other than the standard identifiers outlined above.
\membersection{wxStdDialogButtonSizer::SetCancelButton}\label{wxstddialogbuttonsizersetcancelbutton}
\func{void}{SetCancelButton}{\param{wxButton* }{button}}
-Sets the cancel button for the sizer. This allows you to use IDs other than the standard IDs outlined above.
+Sets the cancel button for the sizer. This allows you to use identifiers other than the standard identifiers outlined above.
\membersection{wxStdDialogButtonSizer::SetNegativeButton}\label{wxstddialogbuttonsizersetnegativebutton}
\func{void}{SetNegativeButton}{\param{wxButton* }{button}}
-Sets the negative button for the sizer. This allows you to use IDs other than the standard IDs outlined above.
+Sets the negative button for the sizer. This allows you to use identifiers other than the standard identifiers outlined above.
+
\section{\class{wxStandardPaths}}\label{wxstandardpaths}
wxStandardPaths returns the standard locations in the file system and should be
-used by the programs to find their data files in a portable way.
+used by applications to find their data files in a portable way.
Please note that this is not a real class because object of this type are never
created but more a namespace containing the class methods which are all static,
\func{static void}{SetInstallPrefix}{\param{const wxString\& }{prefix}}
-\textbf{Note: } This function is only available under Unix.
+\textbf{Note:} This function is only available under Unix.
Lets wxStandardPaths know about the real program installation prefix on a Unix
system. By default, the value returned by
\constfunc{wxFileOffset}{GetLength}{\void}
Returns the length of the stream in bytes. If the length cannot be determined
-(this is always the case for socket streams for example), returns
+(this is always the case for socket streams for example), returns
\texttt{wxInvalidOffset}.
\newsince{2.5.4}
See \helpref{OnSysRead}{wxstreambaseonsysread}.
-
\end{twocollist}
See {\tt samples/widgets} for an example of wxBookCtrl usage.
+
\section{Internationalization}\label{internationalization}
Although internationalization of an application (i18n for short) involves far
-more than just translating its text messages to another message -- date, time and
+more than just translating its text messages to another message - date, time and
currency formats need changing too, some languages are written left to right
and others right to left, character encoding may differ and many other things
-may need changing too -- it is a necessary first step. wxWidgets provides
+may need changing too - it is a necessary first step. wxWidgets provides
facilities for message translation with its
\helpref{wxLocale}{wxlocale} class and is itself fully translated into several
languages. Please consult wxWidgets home page for the most up-to-date
our wxGetTranslation and extracts all strings inside the calls to these
functions. Alternatively, you may use {\tt -a} option to extract all the
strings, but it will usually result in many strings being found which don't
-have to be translated at all. This will create a text message catalog -- a .po
+have to be translated at all. This will create a text message catalog - a .po
file.
\item Translating the strings extracted in the previous step to other
language(s). It involves editing the .po file.
It is expected that the printing code that is currently implemented
in the GNOME print libraries will be moved into GTK+ later.
+
projects / wxWidgets.git / commitdiff
