fixed syntax errors in documentation (once again...)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@17586 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -2119,8 +2119,8 @@ This macro is defined for the platforms with a native 64 bit integer type and
|
||||
allows to define 64 bit compile time constants:
|
||||
|
||||
\begin{verbatim}
|
||||
#ifdef wxLongLong\_t
|
||||
wxLongLong\_t ll = wxLL(0x1234567890abcdef);
|
||||
#ifdef wxLongLong_t
|
||||
wxLongLong_t ll = wxLL(0x1234567890abcdef);
|
||||
#endif
|
||||
\end{verbatim}
|
||||
|
||||
@@ -2135,8 +2135,8 @@ which 64 bit integer numbers (i.e. those of type {\tt wxLongLong\_t}) can be
|
||||
printed. Example of using it:
|
||||
|
||||
\begin{verbatim}
|
||||
#ifdef wxLongLong\_t
|
||||
wxLongLong\_t ll = wxLL(0x1234567890abcdef);
|
||||
#ifdef wxLongLong_t
|
||||
wxLongLong_t ll = wxLL(0x1234567890abcdef);
|
||||
printf("Long long = %" wxLongLongFmtSpec "x\n", ll);
|
||||
#endif
|
||||
\end{verbatim}
|
||||
|
@@ -45,7 +45,7 @@ a similar style to the Microsoft HTML Help viewer and using some of the same fil
|
||||
Although it has an API compatible with other help controllers, it has more advanced features, so it is
|
||||
recommended that you use the specific API for this class instead. Note that if you
|
||||
use .zip or .htb formats for your books, you
|
||||
must add this line to your application initialization: \verb$wxFileSystem::AddHandler(new wxZipFSHandler);$
|
||||
must add this line to your application initialization: {\tt wxFileSystem::AddHandler(new wxZipFSHandler);}
|
||||
or nothing will be shown in your help window.
|
||||
\end{itemize}
|
||||
|
||||
|
@@ -47,7 +47,7 @@ pointer array.
|
||||
\end{verbatim}
|
||||
|
||||
A smart pointer holds a pointer to an object (which must be complete
|
||||
when wxDEFINE_SCOPED_ARRAY() is called). The memory used by the object is
|
||||
when wxDEFINE\_SCOPED\_ARRAY() is called). The memory used by the object is
|
||||
deleted when the smart pointer goes out of scope. The first argument
|
||||
of the macro is the pointer type, the second is the name of the new
|
||||
smart pointer class being created. Below we will use wxScopedArray to
|
||||
|
@@ -47,7 +47,7 @@ pointer array.
|
||||
\end{verbatim}
|
||||
|
||||
A smart pointer holds a pointer to an object (which must be complete
|
||||
when wxDEFINE_SCOPED_PTR() is called). The memory used by the object is
|
||||
when wxDEFINE\_SCOPED\_PTR() is called). The memory used by the object is
|
||||
deleted when the smart pointer goes out of scope. The first argument
|
||||
of the macro is the pointer type, the second is the name of the new
|
||||
smart pointer class being created. Below we will use wxScopedPtr to
|
||||
|
@@ -35,21 +35,21 @@ sent as the user drags the thumbtrack).}
|
||||
|
||||
|
||||
|
||||
\wxheading{The difference between {\tt EVT_SCROLL_THUMBRELEASE} and {\tt EVT_SCROLL_ENDSCROLL}}
|
||||
\wxheading{The difference between {\tt EVT\_SCROLL\_THUMBRELEASE} and {\tt EVT\_SCROLL\_ENDSCROLL}}
|
||||
|
||||
The {\tt EVT_SCROLL_THUMBRELEASE} event is only emitted when actually dragging
|
||||
the thumb using the mouse and releasing it (This {\tt EVT_SCROLL_THUMBRELEASE}
|
||||
event is also followed by an {\tt EVT_SCROLL_ENDSCROLL} event).
|
||||
The {\tt EVT\_SCROLL\_THUMBRELEASE} event is only emitted when actually dragging
|
||||
the thumb using the mouse and releasing it (This {\tt EVT\_SCROLL\_THUMBRELEASE}
|
||||
event is also followed by an {\tt EVT\_SCROLL\_ENDSCROLL} event).
|
||||
|
||||
The {\tt EVT_SCROLL_ENDSCROLL} event also occurs when using the keyboard to
|
||||
The {\tt EVT\_SCROLL\_ENDSCROLL} event also occurs when using the keyboard to
|
||||
change the thumb position, and when clicking next to the thumb (In all these
|
||||
cases the {\tt EVT_SCROLL_THUMBRELEASE} event does not happen).
|
||||
cases the {\tt EVT\_SCROLL\_THUMBRELEASE} event does not happen).
|
||||
|
||||
In short, the {\tt EVT_SCROLL_ENDSCROLL} event is triggered when scrolling/
|
||||
In short, the {\tt EVT\_SCROLL\_ENDSCROLL} event is triggered when scrolling/
|
||||
moving has finished. The only exception (unfortunately) is that changing the
|
||||
thumb position using the mousewheel does give a {\tt EVT_SCROLL_THUMBRELEASE}
|
||||
event but NOT an {\tt EVT_SCROLL_ENDSCROLL} event.
|
||||
thumb position using the mousewheel does give a {\tt EVT\_SCROLL\_THUMBRELEASE}
|
||||
event but NOT an {\tt EVT\_SCROLL\_ENDSCROLL} event.
|
||||
|
||||
Please see the widgets sample ("Slider" page) to see the difference
|
||||
between {\tt EVT_SCROLL_THUMBRELEASE} and {\tt EVT_SCROLL_ENDSCROLL} in action.
|
||||
between {\tt EVT\_SCROLL\_THUMBRELEASE} and {\tt EVT\_SCROLL\_ENDSCROLL} in action.
|
||||
|
||||
|
@@ -60,7 +60,7 @@ Destructor is not virtual, don't use this class polymorphically.
|
||||
\func{wxSemaError }{Post}{\void}
|
||||
|
||||
Increments the semaphore count and signals one of the waiting
|
||||
threads in an atomic way. Returns wxSEMA_OVERFLOW if the count
|
||||
threads in an atomic way. Returns wxSEMA\_OVERFLOW if the count
|
||||
would increase the counter past the maximum.
|
||||
|
||||
\wxheading{Return value}
|
||||
|
Reference in New Issue
Block a user