utils/wxPython/CHANGES.txt

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