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