utils/wxPython/CHANGES.txt

   1 CHANGES.txt for wxPython
   2
   3 ----------------------------------------------------------------------
   4
   5 What's new in 2.1.12
   6 --------------------
   7 Updated wxMVCTree and added a demo for it, also fixed layout on GTK
   8 and some flicker problems.
   9
  10 Added a wrapper class for the Visualization ToolKit (or VTK) in the
  11 wxPython.lib.vtk module.  (http://www.kitware.com/)
  12
  13 Fixed wxTreeCtrl.SetItemImage and GetItemImage to recognise the new
  14 "which" parameter.
  15
  16 Added wxPython.lib.spashscreen from Mike Fletcher.
  17
  18 Added wxPython.lib.filebrowsebutton also from Mike Fletcher.
  19
  20 Renamed wxTreeCtrl.GetParent to GetItemParent to avoid a name clash
  21 with wxWindow.GetParent.
  22
  23 Added wxIntersectRect to compute the intersection of two wxRect's.
  24 It is used like this:
  25
  26    intersect = wxIntersectRect(rect1, rect2)
  27
  28 If r1 and r2 don't intersect then None is returned, otherwise the
  29 rectangle representing the intersection is returned.
  30
  31 Some bug fixes for Clipboard and Drag-n-Drop.
  32
  33
  34
  35
  36 What's new in 2.1.11
  37 --------------------
  38 Skipped a few version numbers so wxMSW, wxGTK and wxPython are all
  39 syncronized.
  40
  41 wxImage.SetData now makes a copy of the image data before giving it to
  42 wxImage.  I mistakenly thought that wxImage would copy the data
  43 itself.
  44
  45 Fixed wxMSW's notebook so the pages get their size set as they are
  46 being added.  This should remove the need for our
  47 wxNotebook.ResizeChildren hack.
  48
  49 wxPanels now support AutoLayout, and wxNotebooks and wxSplitterWindows
  50 no longer tell their children to Layout() themselves.  This will
  51 probably only effect you if you have a wxWindow with AutoLayout inside
  52 a notebook or splitter.  If so, either change it to a wxPanel or add
  53 an EVT_SIZE handler that calls Layout().
  54
  55 Fixed deadlock problem that happened when using threads.
  56
  57 Added new HTML printing classes.
  58
  59 Added wxWindow.GetHandle
  60
  61 Apparently wxMouseEvent.Position has been depreciated in wxWindows as
  62 it is no longer available by default.  You can use GetPositionTuple
  63 (returning a tuple with x,y) instead, or GetPosition (returning a
  64 wxPoint.)
  65
  66 Added wxPostEvent function that allows events to be posted and then
  67 processed later.  This is a thread-safe way to interact with the GUI
  68 thread from other threads.
  69
  70 Added Clipboard and Drag-and-Drop classes.
  71
  72 Added wxFontEnumerator.
  73
  74 Many updates to wxMenu, wxMenuBar.
  75
  76 wxPyEvent and wxPyCommandEvent derived classes now give you the actual
  77 Python object in the event handler instead of a new shadow.
  78
  79 Added a Calendar widget from Lorne White to the library.
  80
  81 Made some fixes to the wxFloatbar.  It still has some troubles on
  82 wxGTK...
  83
  84 Added an MVC tree control from Bryn Keller to the library.
  85
  86
  87
  88
  89 What's new in 2.1.5
  90 -------------------
  91 This is a quick bug-fix release to take care of a few nasties that
  92 crept in at the last minute before 2.1.4 was called done.  No new
  93 major features.
  94
  95
  96
  97 What's new in 2.1.4
  98 --------------------
  99
 100 This release is NOT syncronized with a snapshot release of wxGTK or
 101 wxMSW.  For MSW this isn't much of a problem since you can get the
 102 binaries from the web site.  For other platforms you'll have to build
 103 wxGTK from CVS.  (See http://web.ukonline.co.uk/julian.smart/wxwin/cvs.htm)
 104 To get the same set of sources from CVS that I used, checkout using
 105 the wxPy-2-1-4 tag.
 106
 107 Now back to what's new...
 108
 109 Much more support for event-less callbacks and add-on modules.
 110
 111 Created add-on module with wxOGL classes.
 112
 113 Added wxWindow.GetChildren().  Be careful of this.  It returns a *copy*
 114 of the list of the window's children.  While you are using the list if
 115 anything changes in the real list (a child is deleted, etc.) then the
 116 list you are holding will suddenly have window references to garbage
 117 memory and your app will likely crash.  But if you are careful it works
 118 great!
 119
 120 Added a bunch of new and missing methods to wxTreeCrtl.  The
 121 SortChildren method is now supported, but currently only for the
 122 default sort order.
 123
 124 Added typemaps for wxSize, wxPoint, wxRealPoint, and wxRect that allow
 125 either the actual objects or Python sequence values to be used.  For
 126 example, the following are equivallent:
 127
 128     win = wxWindow(parent, size = wxSize(100, 100))
 129     win = wxWindow(parent, size = (100, 100))
 130
 131 Super-charged the wxHtml module.  You can now create your own tag
 132 handlers and also have access to the parser and cell classes.  There
 133 is a tag handler in the library at wxPython.lib.wxpTag that
 134 understands the WXP tag and is able to place wxPython windows on HTML
 135 pages.  See the demo for an example.
 136
 137 A bunch of the methods of wxMenuBar were previously ifdef'd out for
 138 wxGTK.  Added them back in since the methods exist now.
 139
 140 Wrapped the wxHtmlHelpController and related classes.
 141
 142 Wrapped the C++ versions of wxSizer and friends.  The Python-only
 143 versions are still in the library, but depreciated.  (You will get a
 144 warning message if you try to use them, but the warning can be
 145 disabled.) The usage of the C++ versions is slightly different, and
 146 the functionality of wxBorderSizer is now part of wxBoxSizer.  I have
 147 added a few methods to wxSizer to try and make the transition as
 148 smooth as possible, I combined all Add methods into a single method
 149 that handles all cases, added an AddMany method, etc.  One step I did
 150 not take was to make the default value of flag in the Add method be
 151 wxGROW.  This would have made it more backward compatible, but less
 152 portable to and from wxWin C++ code.  Please see the docs and demo for
 153 further details.
 154
 155 Added wxPyEvent and wxPyCommandEvent classes, derived from wxEvent and
 156 wxCommandEvent.  Each of them has SetPyData and GetPyData methods that
 157 accept or return a single Python object.  You can use these classes
 158 directly or derive from them to create your own types of event objects
 159 that can pass through the wxWindows event system without loosing their
 160 Python parts (as long as they are stored with SetPyData.)  Stay tuned
 161 for more info and examples in future releases.
 162
 163 Added wxPython.lib.grids as an example of how to derive a new sizer
 164 from the C++ sizers.  In this module you will find wxGridSizer and
 165 wxFlexGridSizer.  wxGridSizer arrainges its items in a grid in which
 166 all the widths and heights are the same.  wxFlexgridSizer allows
 167 different widths and heights, and you can also specify rows and/or
 168 columns that are growable.  See the demo for a couple examples for how
 169 to use them.
 170
 171 Added the wxValidator class, and created a class named wxPyValidator
 172 that should be used for the base class of any Python validators.  See
 173 the demo for an example.  Please note that you MUST implement a Clone
 174 method in your validator classes because of the way some things work
 175 in the underlying C++ library.  I did not add wxTextValidator because
 176 of some issues of how it transfers data to and from a wxString, which
 177 in wxPython is automatically translated to and from Python strings, so
 178 there would never be a concrete wxString that would hang around long
 179 enough for the validator to do its job.  On the other hand, it should
 180 be real easy to duplicate the functionality of wxTextValidator in a
 181 pure Python class derived from wxPyValidator.
 182
 183 I've finally added a feature that has been on my list for close to two
 184 years!  Ever wondered what that zero is for when you create your app
 185 object?  Well now you can leave it out or explicitly set it to a true
 186 value.  This value now controls what is to be done with sys.stdout and
 187 sys.stderr.  A false value leaves them alone, and a true value sets
 188 them to an instance of wxPyOnDemandOutputWindow.  (On windows the
 189 default is true, on unix platforms the default is false.)  This class
 190 creates a frame containing a wxTextCtrl as soon as anything is written
 191 to sys.stdout or sys.stderr.  If you close the window it will come
 192 back again the next time something is written.  (You can call
 193 app.RestoreStdio to turn this off.)  If you would rather that the stdio be
 194 redirected to a file, you can provide a second parameter to your app
 195 object's constructor that is a filename.  If you want to use your own
 196 class instead of wxPyOnDemandOutputWindow you can either implement
 197 RedirectStdio() in you app class or change the value of
 198 wxApp.outputWindowClass like this:
 199
 200     class MyApp(wxApp):
 201         outputWindowClass = MyClass
 202
 203         def OnInit(self):
 204             frame = MyFrame()
 205             self.SetTopWindow(frame)
 206             return true
 207
 208 Please see the implementation of wxPyOnDemandOutputWindow and wxApp in
 209 wx.py for more details.  A few words of caution:  if you are running
 210 your app in a debugger, changing sys.stdout and sys.stderr is likely
 211 to really screw things up.
 212
 213 Added wxCaret.  Unfortunately it's author has still not documented it
 214 in the wxWindows docs...
 215
 216 Some new 3rd party contributions in wxPython.lib.  PyShell, in
 217 shell.py is an interesting implementaion of an interactive Python
 218 shell in wxWindows.  floatbar.py has a class derived from wxToolBar
 219 that can sense mouse drags and then reparent itself into another
 220 frame. Moving the new frame close to where it came from puts the tool
 221 bar back into the original parent.  (Unfortunately there is currently
 222 a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
 223 problems...)
 224
 225
 226
 227
 228 What's new in 2.1b3
 229 --------------------
 230
 231 This release is syncronized with release 2.1 snapshot 9 of wxWindows.
 232
 233 Switched to using SWIG from CVS (see http://swig.cs.uchicago.edu/cvs.html)
 234 for some of the new features and such.  Also they have encorporated my
 235 patches so there is really no reason to stick with the current (very
 236 old) release...  This version of SWIG gives the following new
 237 features:
 238
 239     1. Keyword arguments.  You no longer have to specify all the
 240        parameters with defaults to a method just to specify a
 241        non-default value on the end.  You can now do this instead:
 242
 243           win = wxWindow(parent, -1, style = mystyle)
 244
 245     2. There is now an an equivalence between Python's None and C++'s
 246        NULL.  This means that any methods that might return NULL will
 247        now return None and you can use none where wxWindows might be
 248        expecting NULL.  This makes things much more snake-ish.
 249
 250
 251 There is a new build system based on a new Python program instead of
 252 raw makefiles.  Now wxPython builds are virtually the same on MSW or
 253 Unix systems.  See the end of this file for new build instructions and
 254 see distrib/build.py for more details.
 255
 256 wxDC.Bilt now includes the useMask parameter, and has been split into
 257 two different versions.  wxDC.BlitXY is like what was there before and
 258 takes raw coordinants and sizes, and the new wxDC.Blit is for the new
 259 interface using wxPoints and a wxSize.
 260
 261
 262
 263
 264
 265 What's new in 2.1b2
 266 --------------------
 267
 268 Added the missing wxWindow.GetUpdateRegion() method.
 269
 270 Made a new change in SWIG (update your patches everybody) that
 271 provides a fix for global shadow objects that get an exception in
 272 their __del__ when their extension module has already been deleted.
 273 It was only a 1 line change in .../SWIG/Modules/pycpp.cxx at about
 274 line 496 if you want to do it by hand.
 275
 276 It is now possible to run through MainLoop more than once in any one
 277 process.  The cleanup that used to happen as MainLoop completed (and
 278 prevented it from running again) has been delayed until the wxc module
 279 is being unloaded by Python.
 280
 281 I fixed a bunch of stuff in the C++ version of wxGrid so it wouldn't
 282 make wxPython look bad.
 283
 284 wxWindow.PopupMenu() now takes a wxPoint instead of  x,y.  Added
 285 wxWindow.PopupMenuXY to be consistent with some other methods.
 286
 287 Added wxGrid.SetEditInPlace and wxGrid.GetEditInPlace.
 288
 289 You can now provide your own app.MainLoop method.  See
 290 wxPython/demo/demoMainLoop.py for an example and some explaination.
 291
 292 Got the in-place-edit for the wxTreeCtrl fixed and added some demo
 293 code to show how to use it.
 294
 295 Put the wxIcon constructor back in for GTK as it now has one that
 296 matches MSW's.
 297
 298 Added wxGrid.GetCells
 299
 300 Added wxSystemSettings static methods as functions with names like
 301 wxSystemSettings_GetSystemColour.
 302
 303 Removed wxPyMenu since using menu callbacks have been depreciated in
 304 wxWindows.  Use wxMenu and events instead.
 305
 306 Added alternate wxBitmap constructor (for MSW only) as
 307       wxBitmapFromData(data, type, width, height, depth = 1)
 308
 309 Added a helper function named wxPyTypeCast that can convert shadow
 310 objects of one type into shadow objects of another type.  (Like doing
 311 a down-cast.)  See the implementation in wx.py for some docs.
 312
 313 Fixed wxImage GetData and SetData to properly use String objects for
 314 data transfer.
 315
 316 Added access methods to wxGridEvent.
 317
 318 New Makefile/Setup files supporting multiple dynamic extension modules
 319 for unix systems.
 320
 321 Fixes for the wxGLCanvas demo to work around a strange bug in gtk.
 322
 323 SWIG support routines now compiled separately instead of being bundled
 324 in wx.cpp.
 325
 326
 327
 328
 329
 330 What's new in 2.1b1
 331 --------------------
 332 Fixed wxComboBox.SetSelection so that it actually sets the selected
 333 item.  (Actually just removed it from wxPython and let it default to
 334 wxChoice.SetSelection which was already doing the right thing.)
 335
 336 Added the Printing Framework.
 337
 338 Switched back to using the wxWindows DLL for the pre-built Win32
 339 version.  The problem was needing to reinitialize static class info
 340 data after loading each extension module.
 341
 342 Lots of little tweaks and additions to reflect changes to various
 343 wxWindows classes.
 344
 345 Fixed a bug with attaching objects to tree items.  Actually was a
 346 symptom of a larger problem with not obtaining the interpreter lock
 347 when doing any Py_DECREFs.
 348
 349 wxSizer and friends.  Sizers are layout tools that manage a colection
 350 of windows and sizers.  Different types of sizers apply different
 351 types of layout algorithms.  You saw it here first!  These classes are
 352 not even in the wxWindows C++ library yet!
 353
 354
 355
 356 What's new in 2.0b9
 357 -------------------
 358 Bug fix for ListCtrl in test4.py (Was a missing file...  DSM!)
 359
 360 Bug fix for occassional GPF on Win32 systems upon termination of a
 361 wxPython application.
 362
 363 Added wxListBox.GetSelections returning selections as a Tuple.
 364
 365 Added a wxTreeItemData that is able to hold any Python object and be
 366 associated with items in a wxTreeCtrl.  Added test pytree.py to show
 367 this feature off.
 368
 369 Added wxSafeYield function.
 370
 371 OpenGL Canvas can be optionally compiled in to wxPython.
 372
 373 Awesome new Demo Framework for showing off wxPython and for learning
 374 how it all works.
 375
 376 The pre-built Win32 version is no longer distributing the wxWindows
 377 DLL.  It is statically linked with the wxWindows library instead.
 378
 379 Added a couple missing items from the docs.
 380
 381 Added wxImage, wxImageHandler, wxPNGHandler, wxJPEGHandler,
 382 wxGIFHandler and wxBMPHandler.
 383
 384 Added new methods to wxTextCtrl.
 385
 386 Fixed some problems with how SWIG was wrapping some wxTreeCtrl
 387 methods.
 388
 389
 390
 391 What's new in 2.0b8
 392 -------------------
 393 Support for using Python threads in wxPython apps.
 394
 395 Several missing methods from various classes.
 396
 397 Various bug fixes.
 398
 399
 400
 401 What's new in 2.0b7
 402 -------------------
 403 Added DLG_PNT and DLG_SZE convienience methods to wxWindow class.
 404
 405 Added missing constructor and other methods for wxMenuItem.
 406
 407
 408
 409 What's new in 2.0b6
 410 -------------------
 411 Just a quickie update to fix the self-installer to be compatible with
 412 Python 1.5.2b2's Registry settings.
 413
 414
 415 What's new in 2.0b5
 416 -------------------
 417 Well obviously the numbering scheme has changed.  I did this to
 418 reflect the fact that this truly is the second major revision of
 419 wxPython, (well the third actually if you count the one I did for
 420 wxWindows 1.68 and then threw away...) and also that it is associated
 421 with the 2.0 version of wxWindows.
 422
 423 I have finally started documenting wxPython.  There are several pages
 424 in the wxWindows documentation tree specifically about wxPython, and I
 425 have added notes within the class references about where and how wxPython
 426 diverges from wxWindows.
 427
 428 Added wxWindow_FromHWND(hWnd) for wxMSW to construct a wxWindow from a
 429 window handle.  If you can get the window handle into the python code,
 430 it should just work...  More news on this later.
 431
 432 Added wxImageList, wxToolTip.
 433
 434 Re-enabled wxConfig.DeleteAll() since it is reportedly fixed for the
 435 wxRegConfig class.
 436
 437 As usual, some bug fixes, tweaks, etc.
 438
 439
 440
 441 What's new in 0.5.3
 442 -------------------
 443 Added wxSashWindow, wxSashEvent, wxLayoutAlgorithm, etc.
 444
 445 Various cleanup, tweaks, minor additions, etc. to maintain
 446 compatibility with the current wxWindows.
 447
 448
 449
 450 What's new in 0.5.0
 451 -------------------
 452 Changed the import semantics from "from wxPython import *" to "from
 453 wxPython.wx import *"  This is for people who are worried about
 454 namespace pollution, they can use "from wxPython import wx" and then
 455 prefix all the wxPython identifiers with "wx."
 456
 457 Added wxTaskbarIcon for wxMSW.
 458
 459 Made the events work for wxGrid.
 460
 461 Added wxConfig.
 462
 463 Added wxMiniFrame for wxGTK.
 464
 465 Changed many of the args and return values that were pointers to gdi
 466 objects to references to reflect changes in the wxWindows API.
 467
 468 Other assorted fixes and additions.
 469
 470
 471
 472
 473 What's new in 0.4.2
 474 -------------------
 475
 476 wxPython on wxGTK works!!!  Both dynamic and static on Linux and
 477 static on Solaris have been tested.  Many thanks go to Harm
 478 <H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
 479 down a nasty DECREF bug.  Okay so I have to confess that it was just a
 480 DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
 481 because the behavior was so different on different platforms.
 482
 483 The dynamicly loaded module on Solaris is still segfaulting, so it
 484 must have been a different issue all along...
 485
 486
 487
 488 What's New in 0.4
 489 -----------------
 490
 491 1. Worked on wxGTK compatibility.  It is partially working.  On a
 492 Solaris/Sparc box wxPython is working but only when it is statically
 493 linked with the Python interpreter.  When built as a dyamically loaded
 494 extension module, things start acting weirdly and it soon seg-faults.
 495 And on Linux both the statically linked and the dynamically linked
 496 version segfault shortly after starting up.
 497
 498 2. Added Toolbar, StatusBar and SplitterWindow classes.
 499
 500 3. Varioius bug fixes, enhancements, etc.
 501
 502 ----------------------------------------------------------------------