Doc fixes

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_2_BRANCH@7508 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2000-05-29 07:37:24 +00:00
parent 74008a4cd4
commit 70db8eec06
12 changed files with 26 additions and 13 deletions

View File

@@ -13,6 +13,8 @@ wxMSW:
- Various bug fixes - Various bug fixes
- Added wxCHMHelpController, for invoking MS HTML Help - Added wxCHMHelpController, for invoking MS HTML Help
files. This works under VC++ only files. This works under VC++ only
- Modal dialog handling improved
- Printer dialog now modal
wxGTK: wxGTK:

View File

@@ -18,6 +18,13 @@ News
</tr> </tr>
</table> </table>
<H3><a name="release2_1_16">May 24th, 2000</H3><P>
<ul>
<li><a href="download.htm" target=wxmain>wxWindows 2.1.16</a> contains fixes
for wxGTK, wxMSW and wxMotif. It is hoped that this is the last release before the stable 2.2 version.
</ul>
<H3><a name="release2_1_15">March 28th, 2000</H3><P> <H3><a name="release2_1_15">March 28th, 2000</H3><P>
<ul> <ul>

View File

@@ -445,3 +445,4 @@ Returns the date. This function may be called for all event types except
Returns the week day on which the user clicked in Returns the week day on which the user clicked in
{\tt EVT\_CALENDAR\_WEEKDAY\_CLICKED} handler. It doesn't make sense to call {\tt EVT\_CALENDAR\_WEEKDAY\_CLICKED} handler. It doesn't make sense to call
this function in other handlers. this function in other handlers.

View File

@@ -442,3 +442,4 @@ Returns the value of Nth parameter (as string only for now).
\wxheading{See also} \wxheading{See also}
\helpref{GetParamCount}{wxcmdlineparsergetparamcount} \helpref{GetParamCount}{wxcmdlineparsergetparamcount}

View File

@@ -3,7 +3,6 @@
% ../include/wx/strconv.h at 25/Mar/00 10:20:56 % ../include/wx/strconv.h at 25/Mar/00 10:20:56
% %
\section{\class{wxCSConv}}\label{wxcsconv} \section{\class{wxCSConv}}\label{wxcsconv}
This class converts between any character sets and Unicode. This class converts between any character sets and Unicode.
@@ -26,7 +25,6 @@ default user character set.
\latexignore{\rtfignore{\wxheading{Members}}} \latexignore{\rtfignore{\wxheading{Members}}}
\membersection{wxCSConv::wxCSConv}\label{wxcsconvwxcsconv} \membersection{wxCSConv::wxCSConv}\label{wxcsconvwxcsconv}
\func{}{wxCSConv}{\param{const wxChar* }{charset}} \func{}{wxCSConv}{\param{const wxChar* }{charset}}
@@ -59,3 +57,4 @@ Converts from the selected character set to Unicode. Returns the size of the des
\constfunc{size\_t}{WC2MB}{\param{char* }{buf}, \param{const wchar\_t* }{psz}, \param{size\_t }{n}} \constfunc{size\_t}{WC2MB}{\param{char* }{buf}, \param{const wchar\_t* }{psz}, \param{size\_t }{n}}
Converts from Unicode to the selected character set. Returns the size of the destination buffer. Converts from Unicode to the selected character set. Returns the size of the destination buffer.

View File

@@ -48,3 +48,4 @@ Retrieve the current spin button or control value.
\func{void}{SetPosition}{\param{int }{pos}} \func{void}{SetPosition}{\param{int }{pos}}
Set the value associated with the event. Set the value associated with the event.

View File

@@ -174,3 +174,4 @@ If a conversion had taken place in cWX2MB (i.e. in a Unicode build),
the buffer will be deallocated as soon as tmp_buf goes out of scope. the buffer will be deallocated as soon as tmp_buf goes out of scope.
(The macro wxWX2MBbuf reflects the correct return value of cWX2MB (The macro wxWX2MBbuf reflects the correct return value of cWX2MB
(either char* or wxCharBuffer), except for the const.) (either char* or wxCharBuffer), except for the const.)

View File

@@ -60,8 +60,8 @@ wxString internally by wxWindows.
However, there are several problems as well. The most important one is probably However, there are several problems as well. The most important one is probably
that there are often several functions to do exactly the same thing: for that there are often several functions to do exactly the same thing: for
example, to get the length of the string either one of example, to get the length of the string either one of
\helpref{length()}{wxstringlength}, \helpref{Len()}{wxstringlen} or length(), \helpref{Len()}{wxstringlen} or
\helpref{Length()}{wxstringLength} may be used. The first function, as almost \helpref{Length()}{wxstringlength} may be used. The first function, as almost
all the other functions in lowercase, is std::string compatible. The second one all the other functions in lowercase, is std::string compatible. The second one
is "native" wxString version and the last one is wxWindows 1.xx way. So the is "native" wxString version and the last one is wxWindows 1.xx way. So the
question is: which one is better to use? And the answer is that: question is: which one is better to use? And the answer is that:

View File

@@ -169,3 +169,4 @@ This will allow your program to perform conversions between Unicode strings and
ANSI ones (\helpref{wxEncodingConverter}{wxencodingconverter} depends on this ANSI ones (\helpref{wxEncodingConverter}{wxencodingconverter} depends on this
partially) and construct wxString objects from Unicode strings (presumably read partially) and construct wxString objects from Unicode strings (presumably read
from some external file or elsewhere). from some external file or elsewhere).

View File

@@ -42,9 +42,9 @@ the application-wide policy is for 3D controls. Windows only.}
wants to get all char events - even for keys like TAB or ENTER which are wants to get all char events - even for keys like TAB or ENTER which are
usually used for dialog navigation and which wouldn't be generated without usually used for dialog navigation and which wouldn't be generated without
this style} this style}
\twocolitem{\windowstyle{wxNO\_FULLREPAINT\_ON\_RESIZE}}{Disables repainting \twocolitem{\windowstyle{wxNO\_FULL\_REPAINT\_ON\_RESIZE}}{Disables repainting
the window completely when its size is changed - you will have to repaint the the window completely when its size is changed - you will have to repaint the
new window area manually if you use style. Currently only has effect for new window area manually if you use this style. Currently only has an effect for
Windows.} Windows.}
\twocolitem{\windowstyle{wxVSCROLL}}{Use this style to enable a vertical scrollbar. (Still used?) } \twocolitem{\windowstyle{wxVSCROLL}}{Use this style to enable a vertical scrollbar. (Still used?) }
\twocolitem{\windowstyle{wxHSCROLL}}{Use this style to enable a horizontal scrollbar. (Still used?) } \twocolitem{\windowstyle{wxHSCROLL}}{Use this style to enable a horizontal scrollbar. (Still used?) }

View File

@@ -203,9 +203,9 @@ Other string functions.
\helpref{Pad}{wxstringpad}\\ \helpref{Pad}{wxstringpad}\\
\helpref{Truncate}{wxstringtruncate} \helpref{Truncate}{wxstringtruncate}
\membersection{wxWindows 1.xx compatiblity functions} \membersection{wxWindows 1.xx compatibility functions}
These functiosn are deprecated, please consider using new wxWindows 2.0 These functions are deprecated, please consider using new wxWindows 2.0
functions instead of them (or, even better, std::string compatible variants). functions instead of them (or, even better, std::string compatible variants).
\helpref{SubString}{wxstringsubstring}\\ \helpref{SubString}{wxstringsubstring}\\

View File

@@ -51,10 +51,10 @@ Files
----- -----
The distribution is available in archive formats appropriate to the The distribution is available in archive formats appropriate to the
target system. Documentation is available mainly in zip format, target system. Documentation is available mainly in zip format.
and in .tgz format where appropriate. Some add-on libraries (such Some add-on libraries (such as the Object Graphics Library) are
as the Object Graphics Library) are available in zip form only. available in zip form only. In the following, x.y.z represents
In the following, x.y.z represents the current version number. the current version number.
wxWindows for GTK distribution wxWindows for GTK distribution
------------------------------ ------------------------------
@@ -216,5 +216,5 @@ web site) or contact Julian Smart <julian.smart@ukonline.co.uk>.
Good luck! Good luck!
The wxWindows Team, 23rd May, 2000 The wxWindows Team, 24th May, 2000