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
This commit is contained in:
@@ -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
|
||||
|
Reference in New Issue
Block a user