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