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

corrected description of auto-created wxConfig ownership (patch from bug 706868)

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@19950 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2003-04-02 23:20:21 +00:00
parent 49fca29840
commit 736f28f8d8
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -87,9 +87,8 @@ 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 wxWindows will delete this config object for you during the program Note that you must delete this object (usually in \helpref{wxApp::OnExit}{wxapponexit})
shutdown (from \helpref{wxApp::OnExit}{wxapponexit} to be precise) but you can in order to avoid memory leaks, wxWindows won't do it automatically.
also do it yourself earlier if needed.
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