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