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

fixed comment about [not] deleting wxConfig::Get() pointer

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@12693 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin
2001-11-25 18:39:55 +00:00
parent a8141d3f28
commit b52ea5c510
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -86,10 +86,10 @@ instead of creating and deleting the local config objects each time you need
one (especially because creating a wxFileConfig object might be a time 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. Of anywhere in your program, you may access it using the {\it Get()} function.
course, you should delete it on the program termination (otherwise, not only a Note that wxWindows will delete this config object for you during the program
memory leak will result, but even more importantly the changes won't be shutdown (from \helpref{wxApp::OnExit}{wxapponexit} to be precise) but you can
written back!). 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