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

This commit was manufactured by cvs2svn to create tag

Browse Source 
'DEBIAN_2_4_3_1_SARGE_v_2_4_2_4'.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/tags/DEBIAN_2_4_3_1_SARGE_v_2_4_2_4@34395 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2005-05-29 09:56:16 +00:00
parent 86118733af
commit cfd794784f
4010 changed files with 349688 additions and 169530 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
docs/latex/wx/module.tex
View File

@@ -1,13 +1,13 @@
\section{\class{wxModule}}\label{wxmodule}
The module system is a very simple mechanism to allow applications (and parts of wxWindows itself) to
define initialization and cleanup functions that are automatically called on wxWindows
The module system is a very simple mechanism to allow applications (and parts of wxWidgets itself) to
define initialization and cleanup functions that are automatically called on wxWidgets
startup and exit.
To define a new kind of module, derive a class from wxModule, override the OnInit and OnExit functions,
and add the DECLARE\_DYNAMIC\_CLASS and IMPLEMENT\_DYNAMIC\_CLASS to header and implementation files
(which can be the same file). On initialization, wxWindows will find all classes derived from wxModule,
create an instance of each, and call each OnInit function. On exit, wxWindows will call the OnExit
(which can be the same file). On initialization, wxWidgets will find all classes derived from wxModule,
create an instance of each, and call each OnInit function. On exit, wxWidgets will call the OnExit
function for each module instance.
Note that your module class does not have to be in a header file.
@@ -57,28 +57,28 @@ Destructor.
\func{static void}{CleanupModules}{\void}
Calls Exit for each module instance. Called by wxWindows on exit, so there is no
Calls Exit for each module instance. Called by wxWidgets on exit, so there is no
need for an application to call it.
\membersection{wxModule::Exit}\label{wxmoduleexit}
\func{void}{Exit}{\void}
Calls OnExit. This function is called by wxWindows and should not need to be called
Calls OnExit. This function is called by wxWidgets and should not need to be called
by an application.
\membersection{wxModule::Init}\label{wxmoduleinit}
\func{bool}{Init}{\void}
Calls OnInit. This function is called by wxWindows and should not need to be called
Calls OnInit. This function is called by wxWidgets and should not need to be called
by an application.
\membersection{wxModule::InitializeModules}\label{wxmoduleinitializemodules}
\func{static bool}{InitializeModules}{\void}
Calls Init for each module instance. Called by wxWindows on startup, so there is no
Calls Init for each module instance. Called by wxWidgets on startup, so there is no
need for an application to call it.
\membersection{wxModule::OnExit}\label{wxmoduleonexit}
@@ -92,19 +92,19 @@ Provide this function with appropriate cleanup for your module.
\func{virtual bool}{OnInit}{\void}
Provide this function with appropriate initialization for your module. If the function
returns FALSE, wxWindows will exit immediately.
returns FALSE, wxWidgets will exit immediately.
\membersection{wxModule::RegisterModule}\label{wxmoduleregistermodule}
\func{static void}{RegisterModule}{\param{wxModule*}{ module}}
Registers this module with wxWindows. Called by wxWindows on startup, so there is no
Registers this module with wxWidgets. Called by wxWidgets on startup, so there is no
need for an application to call it.
\membersection{wxModule::RegisterModules}\label{wxmoduleregistermodules}
\func{static bool}{RegisterModules}{\void}
Creates instances of and registers all modules. Called by wxWindows on startup, so there is no
Creates instances of and registers all modules. Called by wxWidgets on startup, so there is no
need for an application to call it.