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