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

clarify global wxConfig object life-management

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@39534 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2006-06-03 14:49:23 +00:00
parent 03ead65495
commit 749704355b
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/latex/wx/config.tex
View File

@@ -88,8 +88,10 @@ one (especially because creating a wxFileConfig object might be a time
consuming operation). In this case, you may create this global config object consuming operation). In this case, you may create this global config object
in the very start of the program and {\it Set()} it as the default. Then, from in the very start of the program and {\it Set()} it as the default. Then, from
anywhere in your program, you may access it using the {\it Get()} function. anywhere in your program, you may access it using the {\it Get()} function.
Note that you must delete this object (usually in \helpref{wxApp::OnExit}{wxapponexit}) This global wxConfig object will be deleted by wxWidgets automatically if it
in order to avoid memory leaks, wxWidgets won't do it automatically. exists. Note that this implies that if you do delete this object yourself
(usually in \helpref{wxApp::OnExit}{wxapponexit}) you must use {\it Set(NULL)}
to prevent wxWidgets from deleting it the second time.
As it happens, you may even further simplify the procedure described above: As it happens, you may even further simplify the procedure described above:
you may forget about calling {\it Set()}. When {\it Get()} is called and there you may forget about calling {\it Set()}. When {\it Get()} is called and there