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