From 749704355bd9ca68cfe629aa59af8fabb7dce0ff Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Sat, 3 Jun 2006 14:49:23 +0000 Subject: [PATCH] clarify global wxConfig object life-management git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@39534 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/latex/wx/config.tex | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/latex/wx/config.tex b/docs/latex/wx/config.tex index a9c58e4168..b2969399f7 100644 --- a/docs/latex/wx/config.tex +++ b/docs/latex/wx/config.tex @@ -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 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. -Note that you must delete this object (usually in \helpref{wxApp::OnExit}{wxapponexit}) -in order to avoid memory leaks, wxWidgets won't do it automatically. +This global wxConfig object will be deleted by wxWidgets automatically if it +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: you may forget about calling {\it Set()}. When {\it Get()} is called and there -- 2.45.2