Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Various underscore doc fixes and some wxXCharBuffer documentation.

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@33435 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Ryan Norton
2005-04-08 19:11:58 +00:00
parent 3fa8f7227b
commit 40ca944974
6 changed files with 41 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/latex/wx/wxmsw.tex
View File

@@ -134,7 +134,7 @@ and unregister the button when you're done with it. For example:
win->UnregisterHotKey(0);
\end{verbatim}
You may have to register the buttons in a wxEVT_ACTIVATE event handler
You may have to register the buttons in a wxEVT\_ACTIVATE event handler
since other applications will grab the buttons.
There is currently no method of finding out the names of the special
@@ -165,7 +165,7 @@ and wxTopLevelWindow::SetRightMenu, for example:
#endif
\end{verbatim}
For implementing property sheets (flat tabs), use a wxNotebook with wxNB_FLAT|wxNB_BOTTOM
For implementing property sheets (flat tabs), use a wxNotebook with wxNB\_FLAT|wxNB\_BOTTOM
and have the notebook left, top and right sides overlap the dialog by about 3 pixels
to eliminate spurious borders. You can do this by using a negative spacing in your
sizer Add() call. The cross-platform property sheet dialog \helpref{wxPropertySheetDialog}{wxpropertysheetdialog} is