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