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