Use a working dir for the uninstaller that does exist.

[wxWidgets.git] / wxPython / docs / CHANGES.html

diff --git a/wxPython/docs/CHANGES.html b/wxPython/docs/CHANGES.html
index 06c5334f33811abb8c557a4d41dfb51651f024fc..dd3a665131681b58280daf6d220128a7a1d43f45 100644 (file)
--- a/wxPython/docs/CHANGES.html
+++ b/wxPython/docs/CHANGES.html
@@ -1184,7 +1184,7 @@ an EVT_SIZE handler that calls Layout().</p>
 <p>Fixed deadlock problem that happened when using threads.</p>
 <p>Added new HTML printing classes.</p>
 <p>Added wxWindow.GetHandle</p>
 <p>Fixed deadlock problem that happened when using threads.</p>
 <p>Added new HTML printing classes.</p>
 <p>Added wxWindow.GetHandle</p>

-<p>Apparently wxMouseEvent.Position has been depreciated in wxWindows as
+<p>Apparently wxMouseEvent.Position has been deprecated in wxWindows as

 it is no longer available by default.  You can use GetPositionTuple
 (returning a tuple with x,y) instead, or GetPosition (returning a
 wxPoint.)</p>
 it is no longer available by default.  You can use GetPositionTuple
 (returning a tuple with x,y) instead, or GetPosition (returning a
 wxPoint.)</p>


@@ -1242,7 +1242,7 @@ pages.  See the demo for an example.</p>
 wxGTK.  Added them back in since the methods exist now.</p>
 <p>Wrapped the wxHtmlHelpController and related classes.</p>
 <p>Wrapped the C++ versions of wxSizer and friends.  The Python-only
 wxGTK.  Added them back in since the methods exist now.</p>
 <p>Wrapped the wxHtmlHelpController and related classes.</p>
 <p>Wrapped the C++ versions of wxSizer and friends.  The Python-only

-versions are still in the library, but depreciated.  (You will get a
+versions are still in the library, but deprecated.  (You will get a

 warning message if you try to use them, but the warning can be
 disabled.) The usage of the C++ versions is slightly different, and
 the functionality of wxBorderSizer is now part of wxBoxSizer.  I have
 warning message if you try to use them, but the warning can be
 disabled.) The usage of the C++ versions is slightly different, and
 the functionality of wxBorderSizer is now part of wxBoxSizer.  I have


@@ -1381,7 +1381,7 @@ matches MSW's.</p>
 <p>Added wxGrid.GetCells</p>
 <p>Added wxSystemSettings static methods as functions with names like
 wxSystemSettings_GetSystemColour.</p>
 <p>Added wxGrid.GetCells</p>
 <p>Added wxSystemSettings static methods as functions with names like
 wxSystemSettings_GetSystemColour.</p>

-<p>Removed wxPyMenu since using menu callbacks have been depreciated in
+<p>Removed wxPyMenu since using menu callbacks have been deprecated in

 wxWindows.  Use wxMenu and events instead.</p>
 <dl>
 <dt>Added alternate wxBitmap constructor (for MSW only) as</dt>
 wxWindows.  Use wxMenu and events instead.</p>
 <dl>
 <dt>Added alternate wxBitmap constructor (for MSW only) as</dt>