utils/wxPython/CHANGES.txt

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