wxPython/CHANGES.txt

   1 CHANGES.txt for wxPython
   2
   3 ----------------------------------------------------------------------
   4
   5 New in 2.2.0
   6 ------------
   7
   8 Added wxLog and friends.
   9
  10 Added wxFrame.ShowFullScreen for MSW.
  11
  12 Added PyShellWindow to the wxPython.lib package.
  13
  14
  15
  16 New in 2.1.16
  17 -------------
  18
  19 Added an attribute named labelDelta to the generic buttons that
  20 specifies how far to offset the label when the button is in the
  21 depressed state.
  22
  23 Added wxTipProvider and friends.  See the demo for an example.
  24
  25 wxGrid can now change the cell highlight colour.
  26
  27 Added wxDragImage.
  28
  29 Fixed printing on wxGTK.
  30
  31 Added wxDateTime, wxTimeSpan, and wxDateSpan to wxPython.utils.
  32
  33 Added wxCalendarCtrl.
  34
  35 WARNING: A while back I asked what should be done about the Magic
  36 Method Names.  (Methods that are automatically turned into event
  37 handlers by virtue of their name.)  The consensus was that it is more
  38 confusing to have them than to try and expand them to have greater
  39 coverage.  I am finally getting around to removing the code that
  40 generates the event binding.  This means that if you are using any of
  41 the following method names without a EVT_* call that you need to
  42 modify your code to add the EVT_* to hook the event to the method.
  43
  44     OnChar
  45     OnSize
  46     OnEraseBackground
  47     OnSysColourChanged
  48     OnInitDialog
  49     OnPaint
  50     OnIdle
  51     OnActivate
  52     OnMenuHighlight
  53     OnCloseWindow
  54     OnScroll
  55
  56 Added wxSpinCtrl.
  57
  58
  59
  60
  61 New in 2.1.15
  62 -------------
  63
  64 Fixed wxTreeCtrl.HitTest to return both the tree item as well as the
  65 flags that clairify where the click was in relation to the item.
  66
  67 Fixed thread state problem in wxTreeCtrl.GetBoundingBox and
  68 GetSelections.
  69
  70 Fixed some problems in OGL.  Also wxShape.SetClientData and
  71 .GetClientData can now deal with Python objects.
  72
  73 Added wxListCtrl.SortItems and changed the demo to show how to use it.
  74
  75 Plugged a memory leak.
  76
  77 Wrapped the new wxGrid and friends.  The old wxGrid class is no longer
  78 available.  There are some incompatibilities, and unfortunately the
  79 new classes are not documented yet, (however the methods are more
  80 consistent with each other now so you may be able to guess pretty
  81 good...)
  82
  83 Updated filebrowsebutton.py and calendar.py with changes from their
  84 authors.  There is now a FileBrowseButtonWithHistory class (what a
  85 mouthful!) and wxCalendar has printing support.
  86
  87 Added ActiveXWrapper to the library, and some good demos of it too.
  88 It works great for embedding a COM (a.k.a OCX, a.k.a ActiveX) control
  89 in a window and calling its methods.  It actually creates a new class
  90 on the fly that derives from wxWindow, the COM CoClass and others
  91 needed to make it all work.  The resulting class can be instantiated
  92 just like wxWindow, used in sizers, etc.  It also responds to all COM
  93 method calls, properties, etc., and if the class or a mix-in has
  94 matching method names, then the COM events will be propogated back to
  95 them.
  96
  97 Created a typemap that allows a string to be used for parameters
  98 expecting a wxColour type.  The string is either a colour name as
  99 defined in the wxColourDatabase, or a colour spec of the form
 100 "#RRGGBB".  See the wxStyledTextCtrl demo for an example.
 101
 102 I almost forgot to mention the wxStyledTextCtrl!  Yes, the
 103 wxStyledTextCtrl is finally in wxPython!!  (And the crowd goes
 104 wild...)   There's no documentaTion yet (the crowd boos and hisses...)
 105 but I've included a very readable source file in the
 106 wxPython/demo/data directory, a couple fairly good examples, and you
 107 can also refer to the Scintilla documentaion at
 108 http://www.scintilla.org/ScintillaDoc.html to help fill in the gaps
 109 until the docs are done.  (The croud murmers contentedly as the tool
 110 provider smiles convincingly and removes his flame-proof suit.)
 111
 112
 113
 114
 115 What's new in 2.1.13
 116 --------------------
 117 Skipped a version number to match what has been released for wxGTK.
 118
 119 Updated wxMVCTree and added a demo for it, also fixed layout on GTK
 120 and some flicker problems.
 121
 122 Added a wrapper class for the Visualization ToolKit (or VTK) in the
 123 wxPython.lib.vtk module.  (http://www.kitware.com/)
 124
 125 Fixed wxTreeCtrl.SetItemImage and GetItemImage to recognise the new
 126 "which" parameter.
 127
 128 Added wxPython.lib.spashscreen from Mike Fletcher.
 129
 130 Added wxPython.lib.filebrowsebutton also from Mike Fletcher.
 131
 132 Renamed wxTreeCtrl.GetParent to GetItemParent to avoid a name clash
 133 with wxWindow.GetParent.
 134
 135 Added wxIntersectRect to compute the intersection of two wxRect's.
 136 It is used like this:
 137
 138    intersect = wxIntersectRect(rect1, rect2)
 139
 140 If r1 and r2 don't intersect then None is returned, otherwise the
 141 rectangle representing the intersection is returned.
 142
 143 Some bug fixes for Clipboard and Drag-n-Drop.
 144
 145 Rotated text!!!  WooHoo!  (See wxDC.DrawRotatedText())
 146
 147 Added a set of Generic Buttons to the library.  These are simple
 148 window classes that look and act like native buttons, but you can have
 149 a bit more control over them.  The bezel width can be set in addition
 150 to colours, fonts, etc.  There is a ToggleButton as well as Bitmap
 151 versions too.  They should also serve as a good example of how to
 152 create your own classes derived from wxControl.
 153
 154 The C++ wxToolBar classes have been redone, and so have the wxPython
 155 wrappers.  There have been slight modifications to some of the methods
 156 but shouldn't impact anybody too much.  I took the opportunity to add
 157 support for setting user data on each toolbar tool.  The new AddTool
 158 methods look like this:
 159
 160         def AddTool(ID,
 161                     bitmap,
 162                     pushedBitmap = wxNullBitmap,
 163                     toggle = FALSE,
 164                     clientData = NULL,
 165                     shortHelpString = "",
 166                     longHelpString = "")
 167
 168         def AddSimpleTool(ID,
 169                           bitmap,
 170                           shortHelpString = "",
 171                           longHelpString = "",
 172                           toggle=FALSE)
 173
 174
 175 There are also coresponding InsertTool and InsertSimpleTool methods
 176 that additionally take an integer position as the first parameter.
 177
 178 Added a wrapper for the new PCX and TIFF ImageHandlers.
 179
 180 wxRect now simulates attributes named left, right, top and bottom.
 181
 182 Removed all non wx stuff from the glcanvas module since DA's PyOpenGL
 183 is better and compatible with the wxGLCanvas.  You can get it at
 184 http://starship.python.net:9673/crew/da/Code/PyOpenGL.
 185
 186 Added some missing EVT_ functions.
 187
 188 Added Dirk Holtwic's editor classes to the wxPython.lib.editor
 189 package.
 190
 191 Changed all the "LIST" parameter names to "choices" to match the docs.
 192
 193 More fixes for the wxFloatBar, and it now works on wxGTK even better
 194 than wxMSW!  (The feat is accomplished by using the wxTB_DOCKABLE
 195 style flag instead of trying to float it ourselves.)
 196
 197
 198
 199
 200 What's new in 2.1.11
 201 --------------------
 202 Skipped a few version numbers so wxMSW, wxGTK and wxPython are all
 203 syncronized.
 204
 205 wxImage.SetData now makes a copy of the image data before giving it to
 206 wxImage.  I mistakenly thought that wxImage would copy the data
 207 itself.
 208
 209 Fixed wxMSW's notebook so the pages get their size set as they are
 210 being added.  This should remove the need for our
 211 wxNotebook.ResizeChildren hack.
 212
 213 wxPanels now support AutoLayout, and wxNotebooks and wxSplitterWindows
 214 no longer tell their children to Layout() themselves.  This will
 215 probably only effect you if you have a wxWindow with AutoLayout inside
 216 a notebook or splitter.  If so, either change it to a wxPanel or add
 217 an EVT_SIZE handler that calls Layout().
 218
 219 Fixed deadlock problem that happened when using threads.
 220
 221 Added new HTML printing classes.
 222
 223 Added wxWindow.GetHandle
 224
 225 Apparently wxMouseEvent.Position has been depreciated in wxWindows as
 226 it is no longer available by default.  You can use GetPositionTuple
 227 (returning a tuple with x,y) instead, or GetPosition (returning a
 228 wxPoint.)
 229
 230 Added wxPostEvent function that allows events to be posted and then
 231 processed later.  This is a thread-safe way to interact with the GUI
 232 thread from other threads.
 233
 234 Added Clipboard and Drag-and-Drop classes.
 235
 236 Added wxFontEnumerator.
 237
 238 Many updates to wxMenu, wxMenuBar.
 239
 240 wxPyEvent and wxPyCommandEvent derived classes now give you the actual
 241 Python object in the event handler instead of a new shadow.
 242
 243 Added a Calendar widget from Lorne White to the library.
 244
 245 Made some fixes to the wxFloatbar.  It still has some troubles on
 246 wxGTK...
 247
 248 Added an MVC tree control from Bryn Keller to the library.
 249
 250
 251
 252
 253 What's new in 2.1.5
 254 -------------------
 255 This is a quick bug-fix release to take care of a few nasties that
 256 crept in at the last minute before 2.1.4 was called done.  No new
 257 major features.
 258
 259
 260
 261 What's new in 2.1.4
 262 --------------------
 263
 264 This release is NOT syncronized with a snapshot release of wxGTK or
 265 wxMSW.  For MSW this isn't much of a problem since you can get the
 266 binaries from the web site.  For other platforms you'll have to build
 267 wxGTK from CVS.  (See http://web.ukonline.co.uk/julian.smart/wxwin/cvs.htm)
 268 To get the same set of sources from CVS that I used, checkout using
 269 the wxPy-2-1-4 tag.
 270
 271 Now back to what's new...
 272
 273 Much more support for event-less callbacks and add-on modules.
 274
 275 Created add-on module with wxOGL classes.
 276
 277 Added wxWindow.GetChildren().  Be careful of this.  It returns a *copy*
 278 of the list of the window's children.  While you are using the list if
 279 anything changes in the real list (a child is deleted, etc.) then the
 280 list you are holding will suddenly have window references to garbage
 281 memory and your app will likely crash.  But if you are careful it works
 282 great!
 283
 284 Added a bunch of new and missing methods to wxTreeCrtl.  The
 285 SortChildren method is now supported, but currently only for the
 286 default sort order.
 287
 288 Added typemaps for wxSize, wxPoint, wxRealPoint, and wxRect that allow
 289 either the actual objects or Python sequence values to be used.  For
 290 example, the following are equivallent:
 291
 292     win = wxWindow(parent, size = wxSize(100, 100))
 293     win = wxWindow(parent, size = (100, 100))
 294
 295 Super-charged the wxHtml module.  You can now create your own tag
 296 handlers and also have access to the parser and cell classes.  There
 297 is a tag handler in the library at wxPython.lib.wxpTag that
 298 understands the WXP tag and is able to place wxPython windows on HTML
 299 pages.  See the demo for an example.
 300
 301 A bunch of the methods of wxMenuBar were previously ifdef'd out for
 302 wxGTK.  Added them back in since the methods exist now.
 303
 304 Wrapped the wxHtmlHelpController and related classes.
 305
 306 Wrapped the C++ versions of wxSizer and friends.  The Python-only
 307 versions are still in the library, but depreciated.  (You will get a
 308 warning message if you try to use them, but the warning can be
 309 disabled.) The usage of the C++ versions is slightly different, and
 310 the functionality of wxBorderSizer is now part of wxBoxSizer.  I have
 311 added a few methods to wxSizer to try and make the transition as
 312 smooth as possible, I combined all Add methods into a single method
 313 that handles all cases, added an AddMany method, etc.  One step I did
 314 not take was to make the default value of flag in the Add method be
 315 wxGROW.  This would have made it more backward compatible, but less
 316 portable to and from wxWin C++ code.  Please see the docs and demo for
 317 further details.
 318
 319 Added wxPyEvent and wxPyCommandEvent classes, derived from wxEvent and
 320 wxCommandEvent.  Each of them has SetPyData and GetPyData methods that
 321 accept or return a single Python object.  You can use these classes
 322 directly or derive from them to create your own types of event objects
 323 that can pass through the wxWindows event system without loosing their
 324 Python parts (as long as they are stored with SetPyData.)  Stay tuned
 325 for more info and examples in future releases.
 326
 327 Added wxPython.lib.grids as an example of how to derive a new sizer
 328 from the C++ sizers.  In this module you will find wxGridSizer and
 329 wxFlexGridSizer.  wxGridSizer arrainges its items in a grid in which
 330 all the widths and heights are the same.  wxFlexgridSizer allows
 331 different widths and heights, and you can also specify rows and/or
 332 columns that are growable.  See the demo for a couple examples for how
 333 to use them.
 334
 335 Added the wxValidator class, and created a class named wxPyValidator
 336 that should be used for the base class of any Python validators.  See
 337 the demo for an example.  Please note that you MUST implement a Clone
 338 method in your validator classes because of the way some things work
 339 in the underlying C++ library.  I did not add wxTextValidator because
 340 of some issues of how it transfers data to and from a wxString, which
 341 in wxPython is automatically translated to and from Python strings, so
 342 there would never be a concrete wxString that would hang around long
 343 enough for the validator to do its job.  On the other hand, it should
 344 be real easy to duplicate the functionality of wxTextValidator in a
 345 pure Python class derived from wxPyValidator.
 346
 347 I've finally added a feature that has been on my list for close to two
 348 years!  Ever wondered what that zero is for when you create your app
 349 object?  Well now you can leave it out or explicitly set it to a true
 350 value.  This value now controls what is to be done with sys.stdout and
 351 sys.stderr.  A false value leaves them alone, and a true value sets
 352 them to an instance of wxPyOnDemandOutputWindow.  (On windows the
 353 default is true, on unix platforms the default is false.)  This class
 354 creates a frame containing a wxTextCtrl as soon as anything is written
 355 to sys.stdout or sys.stderr.  If you close the window it will come
 356 back again the next time something is written.  (You can call
 357 app.RestoreStdio to turn this off.)  If you would rather that the stdio be
 358 redirected to a file, you can provide a second parameter to your app
 359 object's constructor that is a filename.  If you want to use your own
 360 class instead of wxPyOnDemandOutputWindow you can either implement
 361 RedirectStdio() in you app class or change the value of
 362 wxApp.outputWindowClass like this:
 363
 364     class MyApp(wxApp):
 365         outputWindowClass = MyClass
 366
 367         def OnInit(self):
 368             frame = MyFrame()
 369             self.SetTopWindow(frame)
 370             return true
 371
 372 Please see the implementation of wxPyOnDemandOutputWindow and wxApp in
 373 wx.py for more details.  A few words of caution:  if you are running
 374 your app in a debugger, changing sys.stdout and sys.stderr is likely
 375 to really screw things up.
 376
 377 Added wxCaret.  Unfortunately it's author has still not documented it
 378 in the wxWindows docs...
 379
 380 Some new 3rd party contributions in wxPython.lib.  PyShell, in
 381 shell.py is an interesting implementaion of an interactive Python
 382 shell in wxWindows.  floatbar.py has a class derived from wxToolBar
 383 that can sense mouse drags and then reparent itself into another
 384 frame. Moving the new frame close to where it came from puts the tool
 385 bar back into the original parent.  (Unfortunately there is currently
 386 a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
 387 problems...)
 388
 389
 390
 391
 392 What's new in 2.1b3
 393 --------------------
 394
 395 This release is syncronized with release 2.1 snapshot 9 of wxWindows.
 396
 397 Switched to using SWIG from CVS (see http://swig.cs.uchicago.edu/cvs.html)
 398 for some of the new features and such.  Also they have encorporated my
 399 patches so there is really no reason to stick with the current (very
 400 old) release...  This version of SWIG gives the following new
 401 features:
 402
 403     1. Keyword arguments.  You no longer have to specify all the
 404        parameters with defaults to a method just to specify a
 405        non-default value on the end.  You can now do this instead:
 406
 407           win = wxWindow(parent, -1, style = mystyle)
 408
 409     2. There is now an an equivalence between Python's None and C++'s
 410        NULL.  This means that any methods that might return NULL will
 411        now return None and you can use none where wxWindows might be
 412        expecting NULL.  This makes things much more snake-ish.
 413
 414
 415 There is a new build system based on a new Python program instead of
 416 raw makefiles.  Now wxPython builds are virtually the same on MSW or
 417 Unix systems.  See the end of this file for new build instructions and
 418 see distrib/build.py for more details.
 419
 420 wxDC.Bilt now includes the useMask parameter, and has been split into
 421 two different versions.  wxDC.BlitXY is like what was there before and
 422 takes raw coordinants and sizes, and the new wxDC.Blit is for the new
 423 interface using wxPoints and a wxSize.
 424
 425
 426
 427
 428
 429 What's new in 2.1b2
 430 --------------------
 431
 432 Added the missing wxWindow.GetUpdateRegion() method.
 433
 434 Made a new change in SWIG (update your patches everybody) that
 435 provides a fix for global shadow objects that get an exception in
 436 their __del__ when their extension module has already been deleted.
 437 It was only a 1 line change in .../SWIG/Modules/pycpp.cxx at about
 438 line 496 if you want to do it by hand.
 439
 440 It is now possible to run through MainLoop more than once in any one
 441 process.  The cleanup that used to happen as MainLoop completed (and
 442 prevented it from running again) has been delayed until the wxc module
 443 is being unloaded by Python.
 444
 445 I fixed a bunch of stuff in the C++ version of wxGrid so it wouldn't
 446 make wxPython look bad.
 447
 448 wxWindow.PopupMenu() now takes a wxPoint instead of  x,y.  Added
 449 wxWindow.PopupMenuXY to be consistent with some other methods.
 450
 451 Added wxGrid.SetEditInPlace and wxGrid.GetEditInPlace.
 452
 453 You can now provide your own app.MainLoop method.  See
 454 wxPython/demo/demoMainLoop.py for an example and some explaination.
 455
 456 Got the in-place-edit for the wxTreeCtrl fixed and added some demo
 457 code to show how to use it.
 458
 459 Put the wxIcon constructor back in for GTK as it now has one that
 460 matches MSW's.
 461
 462 Added wxGrid.GetCells
 463
 464 Added wxSystemSettings static methods as functions with names like
 465 wxSystemSettings_GetSystemColour.
 466
 467 Removed wxPyMenu since using menu callbacks have been depreciated in
 468 wxWindows.  Use wxMenu and events instead.
 469
 470 Added alternate wxBitmap constructor (for MSW only) as
 471       wxBitmapFromData(data, type, width, height, depth = 1)
 472
 473 Added a helper function named wxPyTypeCast that can convert shadow
 474 objects of one type into shadow objects of another type.  (Like doing
 475 a down-cast.)  See the implementation in wx.py for some docs.
 476
 477 Fixed wxImage GetData and SetData to properly use String objects for
 478 data transfer.
 479
 480 Added access methods to wxGridEvent.
 481
 482 New Makefile/Setup files supporting multiple dynamic extension modules
 483 for unix systems.
 484
 485 Fixes for the wxGLCanvas demo to work around a strange bug in gtk.
 486
 487 SWIG support routines now compiled separately instead of being bundled
 488 in wx.cpp.
 489
 490
 491
 492
 493
 494 What's new in 2.1b1
 495 --------------------
 496 Fixed wxComboBox.SetSelection so that it actually sets the selected
 497 item.  (Actually just removed it from wxPython and let it default to
 498 wxChoice.SetSelection which was already doing the right thing.)
 499
 500 Added the Printing Framework.
 501
 502 Switched back to using the wxWindows DLL for the pre-built Win32
 503 version.  The problem was needing to reinitialize static class info
 504 data after loading each extension module.
 505
 506 Lots of little tweaks and additions to reflect changes to various
 507 wxWindows classes.
 508
 509 Fixed a bug with attaching objects to tree items.  Actually was a
 510 symptom of a larger problem with not obtaining the interpreter lock
 511 when doing any Py_DECREFs.
 512
 513 wxSizer and friends.  Sizers are layout tools that manage a colection
 514 of windows and sizers.  Different types of sizers apply different
 515 types of layout algorithms.  You saw it here first!  These classes are
 516 not even in the wxWindows C++ library yet!
 517
 518
 519
 520 What's new in 2.0b9
 521 -------------------
 522 Bug fix for ListCtrl in test4.py (Was a missing file...  DSM!)
 523
 524 Bug fix for occassional GPF on Win32 systems upon termination of a
 525 wxPython application.
 526
 527 Added wxListBox.GetSelections returning selections as a Tuple.
 528
 529 Added a wxTreeItemData that is able to hold any Python object and be
 530 associated with items in a wxTreeCtrl.  Added test pytree.py to show
 531 this feature off.
 532
 533 Added wxSafeYield function.
 534
 535 OpenGL Canvas can be optionally compiled in to wxPython.
 536
 537 Awesome new Demo Framework for showing off wxPython and for learning
 538 how it all works.
 539
 540 The pre-built Win32 version is no longer distributing the wxWindows
 541 DLL.  It is statically linked with the wxWindows library instead.
 542
 543 Added a couple missing items from the docs.
 544
 545 Added wxImage, wxImageHandler, wxPNGHandler, wxJPEGHandler,
 546 wxGIFHandler and wxBMPHandler.
 547
 548 Added new methods to wxTextCtrl.
 549
 550 Fixed some problems with how SWIG was wrapping some wxTreeCtrl
 551 methods.
 552
 553
 554
 555 What's new in 2.0b8
 556 -------------------
 557 Support for using Python threads in wxPython apps.
 558
 559 Several missing methods from various classes.
 560
 561 Various bug fixes.
 562
 563
 564
 565 What's new in 2.0b7
 566 -------------------
 567 Added DLG_PNT and DLG_SZE convienience methods to wxWindow class.
 568
 569 Added missing constructor and other methods for wxMenuItem.
 570
 571
 572
 573 What's new in 2.0b6
 574 -------------------
 575 Just a quickie update to fix the self-installer to be compatible with
 576 Python 1.5.2b2's Registry settings.
 577
 578
 579 What's new in 2.0b5
 580 -------------------
 581 Well obviously the numbering scheme has changed.  I did this to
 582 reflect the fact that this truly is the second major revision of
 583 wxPython, (well the third actually if you count the one I did for
 584 wxWindows 1.68 and then threw away...) and also that it is associated
 585 with the 2.0 version of wxWindows.
 586
 587 I have finally started documenting wxPython.  There are several pages
 588 in the wxWindows documentation tree specifically about wxPython, and I
 589 have added notes within the class references about where and how wxPython
 590 diverges from wxWindows.
 591
 592 Added wxWindow_FromHWND(hWnd) for wxMSW to construct a wxWindow from a
 593 window handle.  If you can get the window handle into the python code,
 594 it should just work...  More news on this later.
 595
 596 Added wxImageList, wxToolTip.
 597
 598 Re-enabled wxConfig.DeleteAll() since it is reportedly fixed for the
 599 wxRegConfig class.
 600
 601 As usual, some bug fixes, tweaks, etc.
 602
 603
 604
 605 What's new in 0.5.3
 606 -------------------
 607 Added wxSashWindow, wxSashEvent, wxLayoutAlgorithm, etc.
 608
 609 Various cleanup, tweaks, minor additions, etc. to maintain
 610 compatibility with the current wxWindows.
 611
 612
 613
 614 What's new in 0.5.0
 615 -------------------
 616 Changed the import semantics from "from wxPython import *" to "from
 617 wxPython.wx import *"  This is for people who are worried about
 618 namespace pollution, they can use "from wxPython import wx" and then
 619 prefix all the wxPython identifiers with "wx."
 620
 621 Added wxTaskbarIcon for wxMSW.
 622
 623 Made the events work for wxGrid.
 624
 625 Added wxConfig.
 626
 627 Added wxMiniFrame for wxGTK.
 628
 629 Changed many of the args and return values that were pointers to gdi
 630 objects to references to reflect changes in the wxWindows API.
 631
 632 Other assorted fixes and additions.
 633
 634
 635
 636
 637 What's new in 0.4.2
 638 -------------------
 639
 640 wxPython on wxGTK works!!!  Both dynamic and static on Linux and
 641 static on Solaris have been tested.  Many thanks go to Harm
 642 <H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
 643 down a nasty DECREF bug.  Okay so I have to confess that it was just a
 644 DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
 645 because the behavior was so different on different platforms.
 646
 647 The dynamicly loaded module on Solaris is still segfaulting, so it
 648 must have been a different issue all along...
 649
 650
 651
 652 What's New in 0.4
 653 -----------------
 654
 655 1. Worked on wxGTK compatibility.  It is partially working.  On a
 656 Solaris/Sparc box wxPython is working but only when it is statically
 657 linked with the Python interpreter.  When built as a dyamically loaded
 658 extension module, things start acting weirdly and it soon seg-faults.
 659 And on Linux both the statically linked and the dynamically linked
 660 version segfault shortly after starting up.
 661
 662 2. Added Toolbar, StatusBar and SplitterWindow classes.
 663
 664 3. Varioius bug fixes, enhancements, etc.
 665
 666 ----------------------------------------------------------------------