Reworked how stock objects are initialized. They now have an

alternate __class__ until the App is initialized so they will raise an
exception if anybody tries to use them before the C++ object has been
created.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@24902 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775

diff --git a/wxPython/docs/MigrationGuide.txt b/wxPython/docs/MigrationGuide.txt
index b0bd3917e1249f2bd19cfeef165782b4563a7f93..73771d24859c66ae3c9e3abdf9b41bca09c41426 100644 (file)
--- a/wxPython/docs/MigrationGuide.txt
+++ b/wxPython/docs/MigrationGuide.txt
@@ -27,9 +27,9 @@ now be the GUI thread instead of the one that imports wxPython.  Some
 potential problems are that the C++ side of the "stock-objects"
 (wx.BLUE_PEN, wx.TheColourDatabase, etc.) are not initialized until
 the wx.App object is created, so you should not use them until after
-you have created your wx.App object.  (In fact, until I find a better
-solution trying to use one of the stock objects before the app is
-created will probably result in a crash.)
+you have created your wx.App object.  If you do then an exception will
+be raised telling you that the C++ object has not bene initialized
+yet.
 
 Also, you will probably not be able to do any kind of GUI or bitmap
 operation unless you first have created an app object, (even on