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