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

documented wxInitialize and wxUnitialize

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@11029 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2001-07-13 23:43:49 +00:00
parent edd03296af
commit 4d01e58361
1 changed files with 59 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

83
docs/latex/wx/function.tex
View File

@@ -1753,6 +1753,54 @@ normal way which usually just means that the application will be terminated.
Calling wxHandleFatalExceptions() with {\it doIt} equal to FALSE will restore Calling wxHandleFatalExceptions() with {\it doIt} equal to FALSE will restore
this default behaviour. this default behaviour.
\membersection{::wxInitAllImageHandlers}\label{wxinitallimagehandlers}
\func{void}{wxInitAllImageHandlers}{\void}
Initializes all available image handlers. For a list of available handlers,
see \helpref{wxImage}{wximage}.
\wxheading{See also}
\helpref{wxImage}{wximage}, \helpref{wxImageHandler}{wximagehandler}
\wxheading{Include files}
<wx/image.h>
\membersection{::wxInitialize}\label{wxinitialize}
\func{bool}{wxInitialize}{\void}
This function is used in wxBase only and only if you don't create
\helpref{wxApp}{wxapp} object at all. In this case you must call it from your
{\tt main()} function before calling any other wxWindows functions.
If the function returns {\tt FALSE} the initialization could not be performed,
in this case the library cannot be used and
\helpref{wxUninitialize}{wxuninitialize} shouldn't be called neither.
This function may be called several times but
\helpref{wxUninitialize}{wxuninitialize} must be called for each successful
call to this function.
\wxheading{Include files}
<wx/app.h>
\membersection{::wxIsBusy}\label{wxisbusy}
\func{bool}{wxIsBusy}{\void}
Returns TRUE if between two \helpref{wxBeginBusyCursor}{wxbeginbusycursor} and\rtfsp
\helpref{wxEndBusyCursor}{wxendbusycursor} calls.
See also \helpref{wxBusyCursor}{wxbusycursor}.
\wxheading{Include files}
<wx/utils.h>
\membersection{::wxKill}\label{wxkill} \membersection{::wxKill}\label{wxkill}
\func{int}{wxKill}{\param{long}{ pid}, \param{int}{ sig = wxSIGTERM}, \param{wxKillError }{*rc = NULL}} \func{int}{wxKill}{\param{long}{ pid}, \param{int}{ sig = wxSIGTERM}, \param{wxKillError }{*rc = NULL}}
@@ -1810,30 +1858,6 @@ enum wxKillError
<wx/utils.h> <wx/utils.h>
\membersection{::wxInitAllImageHandlers}\label{wxinitallimagehandlers}
\func{void}{wxInitAllImageHandlers}{\void}
Initializes all available image handlers. For a list of available handlers,
see \helpref{wxImage}{wximage}.
\wxheading{See also}
\helpref{wxImage}{wximage}, \helpref{wxImageHandler}{wximagehandler}
\membersection{::wxIsBusy}\label{wxisbusy}
\func{bool}{wxIsBusy}{\void}
Returns TRUE if between two \helpref{wxBeginBusyCursor}{wxbeginbusycursor} and\rtfsp
\helpref{wxEndBusyCursor}{wxendbusycursor} calls.
See also \helpref{wxBusyCursor}{wxbusycursor}.
\wxheading{Include files}
<wx/utils.h>
\membersection{::wxLoadUserResource}\label{wxloaduserresource} \membersection{::wxLoadUserResource}\label{wxloaduserresource}
\func{wxString}{wxLoadUserResource}{\param{const wxString\& }{resourceName}, \param{const wxString\& }{resourceType=``TEXT"}} \func{wxString}{wxLoadUserResource}{\param{const wxString\& }{resourceName}, \param{const wxString\& }{resourceType=``TEXT"}}
@@ -2040,6 +2064,17 @@ In release mode this function does nothing.
<wx/debug.h> <wx/debug.h>
\membersection{::wxUninitialize}\label{wxuninitialize}
\func{void}{wxUninitialize}{\void}
This function is for use in console (wxBase) programs only. It must be called
once for each previous successful call to \helpref{wxInitialize}{wxinitialize}.
\wxheading{Include files}
<wx/app.h>
\membersection{::wxUsleep}\label{wxusleep} \membersection{::wxUsleep}\label{wxusleep}
\func{void}{wxUsleep}{\param{unsigned long}{ milliseconds}} \func{void}{wxUsleep}{\param{unsigned long}{ milliseconds}}