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