wxPython documentation updates
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@3210 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
parent
19e0e04b93
commit
dfa13ec8d7
@ -48,9 +48,9 @@ Windows only, I think.
|
||||
\func{}{wxBitmap}{\param{const char}{ bits[]}, \param{int}{ width}, \param{int}{ height}\\
|
||||
\param{int}{ depth = 1}}
|
||||
|
||||
Creates a bitmap from an array of bits.
|
||||
Creates a bitmap from an array of bits.
|
||||
|
||||
Note that the bit depth is ignored on GTK+ and Motif. If you want to create a bitmap
|
||||
Note that the bit depth is ignored on GTK+ and Motif. If you want to create a bitmap
|
||||
from something else than a 1-bit data array, use the \helpref{wxImage}{wximage} class.
|
||||
|
||||
\func{}{wxBitmap}{\param{int}{ width}, \param{int}{ height}, \param{int}{ depth = -1}}
|
||||
@ -143,6 +143,8 @@ Under X, {\it type} defaults to wxBITMAP\_TYPE\_XPM.
|
||||
\pythonnote{Constructors supported by wxPython are:\par
|
||||
\indented{2cm}{\begin{twocollist}
|
||||
\twocolitem{\bf{wxBitmap(name, flag)}}{Loads a bitmap from a file}
|
||||
\twocolitem{\bf{wxBitmap(data, type, width, height, depth=1)}}{Creates
|
||||
a bitmap from the given data, which can be of arbitrary type.}
|
||||
\twocolitem{\bf{wxNoRefBitmap(name, flag)}}{This one won't own the
|
||||
reference, so Python won't call the destructor, this is good for toolbars
|
||||
and such where the parent will manage the bitmap.}
|
||||
|
@ -68,6 +68,9 @@ Returns a system colour.
|
||||
\twocolitem{{\bf wxSYS\_COLOUR\_BTNHILIGHT}}{Same as wxSYS\_COLOUR\_BTNHIGHLIGHT.}
|
||||
\end{twocollist}
|
||||
|
||||
\pythonnote{This static method is implemented in Python as a
|
||||
standalone function named \tt{wxSystemSettings_GetSystemColour}}
|
||||
|
||||
\membersection{wxSystemSettings::GetSystemFont}\label{wxsystemsettingsgetsystemfont}
|
||||
|
||||
\func{static wxFont}{GetSystemFont}{\param{int}{ index}}
|
||||
@ -87,6 +90,9 @@ Returns a system font.
|
||||
Not available in versions of Windows earlier than Windows 95 or Windows NT 4.0.}
|
||||
\end{twocollist}
|
||||
|
||||
\pythonnote{This static method is implemented in Python as a
|
||||
standalone function named \tt{wxSystemSettings_GetSystemFont}}
|
||||
|
||||
\membersection{wxSystemSettings::GetSystemMetric}\label{wxsystemsettingsgetsystemmetric}
|
||||
|
||||
\func{static int}{GetSystemMetric}{\param{int}{ index}}
|
||||
@ -143,3 +149,12 @@ where it would otherwise present the information only in audible form; zero othe
|
||||
\twocolitem{{\bf wxSYS\_SWAP\_BUTTONS}}{Non-zero if the meanings of the left and right mouse buttons are swapped; zero otherwise.}
|
||||
\end{twocollist}
|
||||
|
||||
\pythonnote{This static method is implemented in Python as a
|
||||
standalone function named \tt{wxSystemSettings_GetSystemMetric}}
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -1523,6 +1523,14 @@ Just before the menu is popped up, \helpref{wxMenu::UpdateUI}{wxmenuupdateui} is
|
||||
to ensure that the menu items are in the correct state. The menu does not get deleted
|
||||
by the window.
|
||||
|
||||
\pythonnote{In place of a single overloaded method name, wxPython
|
||||
implements the following methods:\par
|
||||
\indented{2cm}{\begin{twocollist}
|
||||
\twocolitem{\bf{PopupMenu(menu, point)}}{Specifies position with a wxPoint}
|
||||
\twocolitem{\bf{PopupMenuXY(menu, x, y)}}{Specifies position with two integers (x, y)}
|
||||
\end{twocollist}}
|
||||
}
|
||||
|
||||
\membersection{wxWindow::PushEventHandler}\label{wxwindowpusheventhandler}
|
||||
|
||||
\func{void}{PushEventHandler}{\param{wxEvtHandler* }{handler}}
|
||||
|
Loading…
Reference in New Issue
Block a user