wxMemoryDC constructor now optionally accepts a wxBitmap parameter,

[wxWidgets.git] / docs / latex / wx / stackwalker.tex

diff --git a/docs/latex/wx/stackwalker.tex b/docs/latex/wx/stackwalker.tex
index 3d827f4818c4957a8782e5923027a9fa5a1ad044..e99b65774b0f104a01c44ec24c526a0a77ce822e 100644 (file)
--- a/docs/latex/wx/stackwalker.tex
+++ b/docs/latex/wx/stackwalker.tex
@@ -5,16 +5,16 @@
 %% Created:     2005-01-19
 %% RCS-ID:      $Id$
 %% Copyright:   (c) 2005 Vadim Zeitlin
-%% License:     wxWidgets license
+%% License:     wxWindows license
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \section{\class{wxStackWalker}}\label{wxstackwalker}
 
 wxStackWalker allows an application to enumerate, or walk, the stack frames (the function callstack).
-It is mostly useful in only two situations: 
+It is mostly useful in only two situations:
 inside \helpref{wxApp::OnFatalException}{wxapponfatalexception} function to
-programmatically get the location of the crash and, in debug builds, in 
-\helpref{wxApp::OnAssert}{wxapponassert} to report the caller of the failed
+programmatically get the location of the crash and, in debug builds, in
+\helpref{wxApp::OnAssertFailure}{wxapponassertfailure} to report the caller of the failed
 assert.
 
 wxStackWalker works by repeatedly calling
@@ -95,6 +95,6 @@ notice that Walk() frame itself is not included if skip $\ge 1$).
 \func{void}{WalkFromException}{\void}
 
 Enumerate stack frames from the location of uncaught exception.
-This method can only be called from 
+This method can only be called from
 \helpref{wxApp::OnFatalException()}{wxapponfatalexception}.