Some fixes (&->\&, _->\_) to remove latex complaints.
Actually the whole point of this excercise was to try to make a nice pdf file with contents tree and thumbnail pages using pdflatex, but it keeps depleting tex's resources :-( git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@5884 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -321,7 +321,7 @@ Gets the width of the bitmap in pixels.
|
||||
|
||||
\membersection{wxBitmap::GetSubBitmap}\label{wxbitmapgetsubbitmap}
|
||||
|
||||
\constfunc{wxBitmap}{GetSubBitmap}{\param{const wxRect&}{rect}}
|
||||
\constfunc{wxBitmap}{GetSubBitmap}{\param{const wxRect\&}{rect}}
|
||||
|
||||
Returns a sub bitmap of the current one as long as the rect belongs entirely to
|
||||
the bitmap. This function preserves bit depth and mask information.
|
||||
|
@@ -7,7 +7,7 @@
|
||||
|
||||
This class is capable of converting strings between any two
|
||||
8-bit encodings/charsets. It can also convert from/to Unicode (but only
|
||||
if you compiled wxWindows with wxUSE_UNICODE set to 1).
|
||||
if you compiled wxWindows with wxUSE\_UNICODE set to 1).
|
||||
|
||||
\wxheading{Derived from}
|
||||
|
||||
|
@@ -127,7 +127,7 @@ with full MIME type specification for this file type: for example, "text/plain".
|
||||
|
||||
\membersection{wxFileType::GetMimeTypes}\label{wxfiletypegetmimetypes}
|
||||
|
||||
\func{bool}{GetMimeType}{\param{wxArrayString&}{ mimeTypes}}
|
||||
\func{bool}{GetMimeType}{\param{wxArrayString\&}{ mimeTypes}}
|
||||
|
||||
Same as \helpref{GetMimeType}{wxfiletypegetmimetype} but returns array of MIME
|
||||
types. This array will contain only one item in most cases but sometimes,
|
||||
|
@@ -88,7 +88,7 @@ a directory.
|
||||
|
||||
\membersection{::wxFileModificationTime}
|
||||
|
||||
\func{time_t}{wxFileModificationTime}{\param{const wxString\& }{filename}}
|
||||
\func{time\_t}{wxFileModificationTime}{\param{const wxString\& }{filename}}
|
||||
|
||||
Returns time of last modification of given file.
|
||||
|
||||
|
@@ -197,7 +197,7 @@ before calling Layout.
|
||||
|
||||
\membersection{wxHtmlCell::OnMouseClick}\label{wxhtmlcellonmouseclick}
|
||||
|
||||
\func{virtual void}{OnMouseClick}{\param{wxWindow* }{parent}, \param{int }{x}, \param{int }{y}, \param{const wxMouseEvent& }{event}}
|
||||
\func{virtual void}{OnMouseClick}{\param{wxWindow* }{parent}, \param{int}{x}, \param{int }{y}, \param{const wxMouseEvent\& }{event}}
|
||||
|
||||
This function is simple event handler. Each time user clicks mouse button over a cell
|
||||
within \helpref{wxHtmlWindow}{wxhtmlwindow} this method of that cell is called. Default behavior is
|
||||
|
@@ -28,7 +28,7 @@ location of .hhp file.
|
||||
Charset=@rfc_charset@
|
||||
\end{verbatim}
|
||||
|
||||
which specifies what charset (e.g. "iso8859_1") was used in contents
|
||||
which specifies what charset (e.g. "iso8859\_1") was used in contents
|
||||
and index files. Please note that this line is incompatible with
|
||||
MS HTML Help Workshop and it would either silently remove it or complain
|
||||
with some error. See also
|
||||
|
@@ -131,7 +131,7 @@ FALSE if an error occured, TRUE otherwise
|
||||
|
||||
\membersection{wxHtmlWindow::OnLinkClicked}\label{wxhtmlwindowonlinkclicked}
|
||||
|
||||
\func{virtual void}{OnLinkClicked}{\param{const wxHtmlLinkInfo& }{link}}
|
||||
\func{virtual void}{OnLinkClicked}{\param{const wxHtmlLinkInfo\& }{link}}
|
||||
|
||||
Called when user clicks on hypertext link. Default behaviour is to call
|
||||
\helpref{LoadPage}{wxhtmlwindowloadpage} and do nothing else.
|
||||
|
@@ -1,7 +1,8 @@
|
||||
\section{\class{wxMemoryDC}}\label{wxmemorydc}
|
||||
|
||||
A memory device context provides a means to draw graphics onto a bitmap. When
|
||||
drawing in to a mono-bitmap, using {\tt wxWHITE}, {\tt wxWHITE_PEN} and {\tt wxWHITE_BRUSH}
|
||||
drawing in to a mono-bitmap, using {\tt wxWHITE}, {\tt wxWHITE\_PEN} and
|
||||
{\tt wxWHITE\_BRUSH}
|
||||
will draw the background colour (i.e. 0) whereas all other colours will draw the
|
||||
foreground colour (i.e. 1).
|
||||
|
||||
|
@@ -502,7 +502,7 @@ menu bar.}
|
||||
|
||||
\docparam{titles}{An array of title strings. Deallocate this array after creating the menu bar.}
|
||||
|
||||
\docparam{style}{If {\tt wxMB_DOCKABLE} the menu bar can be detached (wxGTK only).}
|
||||
\docparam{style}{If {\tt wxMB\_DOCKABLE} the menu bar can be detached (wxGTK only).}
|
||||
|
||||
\pythonnote{Only the default constructor is supported in wxPython.
|
||||
Use wxMenuBar.Append instead.}
|
||||
|
@@ -311,8 +311,8 @@ the \helpref{wxTextCtrl}{wxtextctrl} class (single line, multi line, read only,
|
||||
password, ignoring TAB, ignoring ENTER).
|
||||
|
||||
Secondly it shows how to intercept a \helpref{wxKeyEvent}{wxkeyevent} in both
|
||||
the raw form using the {\tt EVT_KEY_UP} and {\tt EVT_KEY_DOWN} macros and the
|
||||
higherlevel from using the {\tt EVT_CHAR} macro. All characters will be logged
|
||||
the raw form using the {\tt EVT\_KEY\_UP} and {\tt EVT\_KEY\_DOWN} macros and the
|
||||
higherlevel from using the {\tt EVT\_CHAR} macro. All characters will be logged
|
||||
in a log window at the bottom of the main window. By pressing some of the function
|
||||
keys, you can test some actions in the text ctrl as well as get statitics on the
|
||||
text ctrls, which is useful for testing if these statitics actually are correct.
|
||||
|
Reference in New Issue
Block a user