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