]> git.saurik.com Git - wxWidgets.git/blame_incremental - wxPython/CHANGES.txt
fixed all's dependencies so that the makefile generates files.lst files
[wxWidgets.git] / wxPython / CHANGES.txt
... / ...
CommitLineData
1CHANGES.txt for wxPython
2
3----------------------------------------------------------------------
4
5
62.2.5
7-----
8
9New typemaps for wxString when compiling for Python 2.0 and beyond
10that allow Unicode objects to be passed as well as String objects. If
11a Unicode object is passed PyString_AsStringAndSize is used to convert
12it to a wxString using the default encoding.
13
14Fixed the generic buttons so tool tips work for them.
15
16Fixed a bug in the demo's tree control.
17
18Added a listbox to the listbox demo that shows how to find items with
19a matching prefix as keys are typed.
20
21Added code to the wxListCtrl demo to show how to get text from a
22column in report mode.
23
24Added code to the toolbar demo to clear the long help from the status
25bar after 2 seconds.
26
27Added wxJoystick.
28
29Fixed wxTimer so it can be used as described in the docs, either with
30a Notify method in a subclass, or sending an event to a wxEvtHandler
31object, (usually a window.)
32
33Added wxNotifyEvent.Allow()
34
35Fixed GOBS of reference leaks.
36
37Massive code changes and cleanup to allow wxPython to be split into
38multiple extension modules again. A Python CObject is used to allow
39the "export" of SWIG functions and other common helper functions from
40the wxc module to other modules, even if they are in separate shared
41libraries. Should also be usable from 3rd party code, just include
42wxPython/src/export.h
43
44Changed the default setup so the following are built as separate
45extension modules: calendar, glcanvas, grid, html, ogl, stc, and
46utils. Will probably add more later.
47
48Changed the wxPrinterDC to use the new constructor taking a
49wxPrintData object. The old ctor is still there using the
50wxPrinterDC2 name.
51
52Added wxPython.lib.anchors.py from Riaan Booysen. It contains a class
53that implements Delphi's Anchors with wxLayoutConstraints.
54
55Added wxPython.lib.fancytext from Timothy Hochberg.
56
57Changed the GenericButtons to send their event in idle time, so the
58mouse won't be captured when the event handler is called.
59
60Added wxPython.lib.rpcMixin from Greg Landrum, although it's not
61integrated with the demo yet. It allows a wxPython GUI to be an
62XML-RPC server.
63
64
65
66New in 2.2.2
67------------
68
69Significantly changed how the wxStyledtextCtrl code that wraps
70Scintilla is implemented. Most of it is now automatically generated
71from an interface definition file provided by Scintilla. This means
72that it will be much easier to stay in sync with new Scintilla
73releases, but also means that some of the method and identifier names
74have changed. See wxPython/demo/data/stc.h for a copy of the C++
75interface from which the Python interface is generated. There is now
76some inline documentation in that file that should really help explain
77how things work.
78
79I am now using the Python Distutils to build wxPython and to make some
80of the distribution files. (See http://www.python.org/sigs/distutils-sig/)
81This means no more messing with my kludgy build.py/Makefile hack,
82builds will be more consistent with other Python extensions that also
83use Distutils, and will hopefully make wxPython easier to build for
84platforms where there have been troubles before. If you are building
85wxPython for Python 1.5.2 or for 1.6, then you will need to get and
86install version 1.0 of Distutils from the website above. If you are
87using Python 2.0 then you already have it.
88
89Added wxInputStream and the wxFileSystem family of classes,
90contributed by Joerg Baumann.
91
92Added wxProcess and support for it to wxExecute. wxProcess lets you
93get notified when an asyncronous child process terminates, and also to
94get input/output streams for the child process's stdout, stderr and
95stdin.
96
97Removed the old python sizers.
98
99Added __add__, __sub__ and __cmp__ (equality check only) for wxPoint
100and wxRealPoint.
101
102Changed the build to make one big extension module instead of one for
103the core and each contrib. This allowed me to do away with the
104libwxPyHelpers.so on unix systems.
105
106Lots of little fixes here and there.
107
108Some hacks on wxGTK to try and make the AutoComplete listbox in the
109wxStyledTextCtrl to behave better. It's still not as nice as on
110wxMSW, but at least it's a bit more usable now.
111
112
113
114
115New in 2.2.1
116------------
117
118Various tweaks, fixes, missing methods, etc.
119
120Added example use of wxTaskBarIcon to the demo.
121
122
123
124New in 2.2.0
125------------
126
127Added wxLog and friends.
128
129Added wxFrame.ShowFullScreen for MSW.
130
131Added PyShellWindow to the wxPython.lib package.
132
133
134
135New in 2.1.16
136-------------
137
138Added an attribute named labelDelta to the generic buttons that
139specifies how far to offset the label when the button is in the
140depressed state.
141
142Added wxTipProvider and friends. See the demo for an example.
143
144wxGrid can now change the cell highlight colour.
145
146Added wxDragImage.
147
148Fixed printing on wxGTK.
149
150Added wxDateTime, wxTimeSpan, and wxDateSpan to wxPython.utils.
151
152Added wxCalendarCtrl.
153
154WARNING: A while back I asked what should be done about the Magic
155Method Names. (Methods that are automatically turned into event
156handlers by virtue of their name.) The consensus was that it is more
157confusing to have them than to try and expand them to have greater
158coverage. I am finally getting around to removing the code that
159generates the event binding. This means that if you are using any of
160the following method names without a EVT_* call that you need to
161modify your code to add the EVT_* to hook the event to the method.
162
163 OnChar
164 OnSize
165 OnEraseBackground
166 OnSysColourChanged
167 OnInitDialog
168 OnPaint
169 OnIdle
170 OnActivate
171 OnMenuHighlight
172 OnCloseWindow
173 OnScroll
174
175Added wxSpinCtrl.
176
177
178
179
180New in 2.1.15
181-------------
182
183Fixed wxTreeCtrl.HitTest to return both the tree item as well as the
184flags that clairify where the click was in relation to the item.
185
186Fixed thread state problem in wxTreeCtrl.GetBoundingBox and
187GetSelections.
188
189Fixed some problems in OGL. Also wxShape.SetClientData and
190.GetClientData can now deal with Python objects.
191
192Added wxListCtrl.SortItems and changed the demo to show how to use it.
193
194Plugged a memory leak.
195
196Wrapped the new wxGrid and friends. The old wxGrid class is no longer
197available. There are some incompatibilities, and unfortunately the
198new classes are not documented yet, (however the methods are more
199consistent with each other now so you may be able to guess pretty
200good...)
201
202Updated filebrowsebutton.py and calendar.py with changes from their
203authors. There is now a FileBrowseButtonWithHistory class (what a
204mouthful!) and wxCalendar has printing support.
205
206Added ActiveXWrapper to the library, and some good demos of it too.
207It works great for embedding a COM (a.k.a OCX, a.k.a ActiveX) control
208in a window and calling its methods. It actually creates a new class
209on the fly that derives from wxWindow, the COM CoClass and others
210needed to make it all work. The resulting class can be instantiated
211just like wxWindow, used in sizers, etc. It also responds to all COM
212method calls, properties, etc., and if the class or a mix-in has
213matching method names, then the COM events will be propogated back to
214them.
215
216Created a typemap that allows a string to be used for parameters
217expecting a wxColour type. The string is either a colour name as
218defined in the wxColourDatabase, or a colour spec of the form
219"#RRGGBB". See the wxStyledTextCtrl demo for an example.
220
221I almost forgot to mention the wxStyledTextCtrl! Yes, the
222wxStyledTextCtrl is finally in wxPython!! (And the crowd goes
223wild...) There's no documentaTion yet (the crowd boos and hisses...)
224but I've included a very readable source file in the
225wxPython/demo/data directory, a couple fairly good examples, and you
226can also refer to the Scintilla documentaion at
227http://www.scintilla.org/ScintillaDoc.html to help fill in the gaps
228until the docs are done. (The croud murmers contentedly as the tool
229provider smiles convincingly and removes his flame-proof suit.)
230
231
232
233
234What's new in 2.1.13
235--------------------
236Skipped a version number to match what has been released for wxGTK.
237
238Updated wxMVCTree and added a demo for it, also fixed layout on GTK
239and some flicker problems.
240
241Added a wrapper class for the Visualization ToolKit (or VTK) in the
242wxPython.lib.vtk module. (http://www.kitware.com/)
243
244Fixed wxTreeCtrl.SetItemImage and GetItemImage to recognise the new
245"which" parameter.
246
247Added wxPython.lib.spashscreen from Mike Fletcher.
248
249Added wxPython.lib.filebrowsebutton also from Mike Fletcher.
250
251Renamed wxTreeCtrl.GetParent to GetItemParent to avoid a name clash
252with wxWindow.GetParent.
253
254Added wxIntersectRect to compute the intersection of two wxRect's.
255It is used like this:
256
257 intersect = wxIntersectRect(rect1, rect2)
258
259If r1 and r2 don't intersect then None is returned, otherwise the
260rectangle representing the intersection is returned.
261
262Some bug fixes for Clipboard and Drag-n-Drop.
263
264Rotated text!!! WooHoo! (See wxDC.DrawRotatedText())
265
266Added a set of Generic Buttons to the library. These are simple
267window classes that look and act like native buttons, but you can have
268a bit more control over them. The bezel width can be set in addition
269to colours, fonts, etc. There is a ToggleButton as well as Bitmap
270versions too. They should also serve as a good example of how to
271create your own classes derived from wxControl.
272
273The C++ wxToolBar classes have been redone, and so have the wxPython
274wrappers. There have been slight modifications to some of the methods
275but shouldn't impact anybody too much. I took the opportunity to add
276support for setting user data on each toolbar tool. The new AddTool
277methods look like this:
278
279 def AddTool(ID,
280 bitmap,
281 pushedBitmap = wxNullBitmap,
282 toggle = FALSE,
283 clientData = NULL,
284 shortHelpString = "",
285 longHelpString = "")
286
287 def AddSimpleTool(ID,
288 bitmap,
289 shortHelpString = "",
290 longHelpString = "",
291 toggle=FALSE)
292
293
294There are also coresponding InsertTool and InsertSimpleTool methods
295that additionally take an integer position as the first parameter.
296
297Added a wrapper for the new PCX and TIFF ImageHandlers.
298
299wxRect now simulates attributes named left, right, top and bottom.
300
301Removed all non wx stuff from the glcanvas module since DA's PyOpenGL
302is better and compatible with the wxGLCanvas. You can get it at
303http://starship.python.net:9673/crew/da/Code/PyOpenGL.
304
305Added some missing EVT_ functions.
306
307Added Dirk Holtwic's editor classes to the wxPython.lib.editor
308package.
309
310Changed all the "LIST" parameter names to "choices" to match the docs.
311
312More fixes for the wxFloatBar, and it now works on wxGTK even better
313than wxMSW! (The feat is accomplished by using the wxTB_DOCKABLE
314style flag instead of trying to float it ourselves.)
315
316
317
318
319What's new in 2.1.11
320--------------------
321Skipped a few version numbers so wxMSW, wxGTK and wxPython are all
322syncronized.
323
324wxImage.SetData now makes a copy of the image data before giving it to
325wxImage. I mistakenly thought that wxImage would copy the data
326itself.
327
328Fixed wxMSW's notebook so the pages get their size set as they are
329being added. This should remove the need for our
330wxNotebook.ResizeChildren hack.
331
332wxPanels now support AutoLayout, and wxNotebooks and wxSplitterWindows
333no longer tell their children to Layout() themselves. This will
334probably only effect you if you have a wxWindow with AutoLayout inside
335a notebook or splitter. If so, either change it to a wxPanel or add
336an EVT_SIZE handler that calls Layout().
337
338Fixed deadlock problem that happened when using threads.
339
340Added new HTML printing classes.
341
342Added wxWindow.GetHandle
343
344Apparently wxMouseEvent.Position has been depreciated in wxWindows as
345it is no longer available by default. You can use GetPositionTuple
346(returning a tuple with x,y) instead, or GetPosition (returning a
347wxPoint.)
348
349Added wxPostEvent function that allows events to be posted and then
350processed later. This is a thread-safe way to interact with the GUI
351thread from other threads.
352
353Added Clipboard and Drag-and-Drop classes.
354
355Added wxFontEnumerator.
356
357Many updates to wxMenu, wxMenuBar.
358
359wxPyEvent and wxPyCommandEvent derived classes now give you the actual
360Python object in the event handler instead of a new shadow.
361
362Added a Calendar widget from Lorne White to the library.
363
364Made some fixes to the wxFloatbar. It still has some troubles on
365wxGTK...
366
367Added an MVC tree control from Bryn Keller to the library.
368
369
370
371
372What's new in 2.1.5
373-------------------
374This is a quick bug-fix release to take care of a few nasties that
375crept in at the last minute before 2.1.4 was called done. No new
376major features.
377
378
379
380What's new in 2.1.4
381--------------------
382
383This release is NOT syncronized with a snapshot release of wxGTK or
384wxMSW. For MSW this isn't much of a problem since you can get the
385binaries from the web site. For other platforms you'll have to build
386wxGTK from CVS. (See http://web.ukonline.co.uk/julian.smart/wxwin/cvs.htm)
387To get the same set of sources from CVS that I used, checkout using
388the wxPy-2-1-4 tag.
389
390Now back to what's new...
391
392Much more support for event-less callbacks and add-on modules.
393
394Created add-on module with wxOGL classes.
395
396Added wxWindow.GetChildren(). Be careful of this. It returns a *copy*
397of the list of the window's children. While you are using the list if
398anything changes in the real list (a child is deleted, etc.) then the
399list you are holding will suddenly have window references to garbage
400memory and your app will likely crash. But if you are careful it works
401great!
402
403Added a bunch of new and missing methods to wxTreeCrtl. The
404SortChildren method is now supported, but currently only for the
405default sort order.
406
407Added typemaps for wxSize, wxPoint, wxRealPoint, and wxRect that allow
408either the actual objects or Python sequence values to be used. For
409example, the following are equivallent:
410
411 win = wxWindow(parent, size = wxSize(100, 100))
412 win = wxWindow(parent, size = (100, 100))
413
414Super-charged the wxHtml module. You can now create your own tag
415handlers and also have access to the parser and cell classes. There
416is a tag handler in the library at wxPython.lib.wxpTag that
417understands the WXP tag and is able to place wxPython windows on HTML
418pages. See the demo for an example.
419
420A bunch of the methods of wxMenuBar were previously ifdef'd out for
421wxGTK. Added them back in since the methods exist now.
422
423Wrapped the wxHtmlHelpController and related classes.
424
425Wrapped the C++ versions of wxSizer and friends. The Python-only
426versions are still in the library, but depreciated. (You will get a
427warning message if you try to use them, but the warning can be
428disabled.) The usage of the C++ versions is slightly different, and
429the functionality of wxBorderSizer is now part of wxBoxSizer. I have
430added a few methods to wxSizer to try and make the transition as
431smooth as possible, I combined all Add methods into a single method
432that handles all cases, added an AddMany method, etc. One step I did
433not take was to make the default value of flag in the Add method be
434wxGROW. This would have made it more backward compatible, but less
435portable to and from wxWin C++ code. Please see the docs and demo for
436further details.
437
438Added wxPyEvent and wxPyCommandEvent classes, derived from wxEvent and
439wxCommandEvent. Each of them has SetPyData and GetPyData methods that
440accept or return a single Python object. You can use these classes
441directly or derive from them to create your own types of event objects
442that can pass through the wxWindows event system without loosing their
443Python parts (as long as they are stored with SetPyData.) Stay tuned
444for more info and examples in future releases.
445
446Added wxPython.lib.grids as an example of how to derive a new sizer
447from the C++ sizers. In this module you will find wxGridSizer and
448wxFlexGridSizer. wxGridSizer arrainges its items in a grid in which
449all the widths and heights are the same. wxFlexgridSizer allows
450different widths and heights, and you can also specify rows and/or
451columns that are growable. See the demo for a couple examples for how
452to use them.
453
454Added the wxValidator class, and created a class named wxPyValidator
455that should be used for the base class of any Python validators. See
456the demo for an example. Please note that you MUST implement a Clone
457method in your validator classes because of the way some things work
458in the underlying C++ library. I did not add wxTextValidator because
459of some issues of how it transfers data to and from a wxString, which
460in wxPython is automatically translated to and from Python strings, so
461there would never be a concrete wxString that would hang around long
462enough for the validator to do its job. On the other hand, it should
463be real easy to duplicate the functionality of wxTextValidator in a
464pure Python class derived from wxPyValidator.
465
466I've finally added a feature that has been on my list for close to two
467years! Ever wondered what that zero is for when you create your app
468object? Well now you can leave it out or explicitly set it to a true
469value. This value now controls what is to be done with sys.stdout and
470sys.stderr. A false value leaves them alone, and a true value sets
471them to an instance of wxPyOnDemandOutputWindow. (On windows the
472default is true, on unix platforms the default is false.) This class
473creates a frame containing a wxTextCtrl as soon as anything is written
474to sys.stdout or sys.stderr. If you close the window it will come
475back again the next time something is written. (You can call
476app.RestoreStdio to turn this off.) If you would rather that the stdio be
477redirected to a file, you can provide a second parameter to your app
478object's constructor that is a filename. If you want to use your own
479class instead of wxPyOnDemandOutputWindow you can either implement
480RedirectStdio() in you app class or change the value of
481wxApp.outputWindowClass like this:
482
483 class MyApp(wxApp):
484 outputWindowClass = MyClass
485
486 def OnInit(self):
487 frame = MyFrame()
488 self.SetTopWindow(frame)
489 return true
490
491Please see the implementation of wxPyOnDemandOutputWindow and wxApp in
492wx.py for more details. A few words of caution: if you are running
493your app in a debugger, changing sys.stdout and sys.stderr is likely
494to really screw things up.
495
496Added wxCaret. Unfortunately it's author has still not documented it
497in the wxWindows docs...
498
499Some new 3rd party contributions in wxPython.lib. PyShell, in
500shell.py is an interesting implementaion of an interactive Python
501shell in wxWindows. floatbar.py has a class derived from wxToolBar
502that can sense mouse drags and then reparent itself into another
503frame. Moving the new frame close to where it came from puts the tool
504bar back into the original parent. (Unfortunately there is currently
505a bug in wxGTK's wxFrame.SetToolBar so the FloatBar has some
506problems...)
507
508
509
510
511What's new in 2.1b3
512--------------------
513
514This release is syncronized with release 2.1 snapshot 9 of wxWindows.
515
516Switched to using SWIG from CVS (see http://swig.cs.uchicago.edu/cvs.html)
517for some of the new features and such. Also they have encorporated my
518patches so there is really no reason to stick with the current (very
519old) release... This version of SWIG gives the following new
520features:
521
522 1. Keyword arguments. You no longer have to specify all the
523 parameters with defaults to a method just to specify a
524 non-default value on the end. You can now do this instead:
525
526 win = wxWindow(parent, -1, style = mystyle)
527
528 2. There is now an an equivalence between Python's None and C++'s
529 NULL. This means that any methods that might return NULL will
530 now return None and you can use none where wxWindows might be
531 expecting NULL. This makes things much more snake-ish.
532
533
534There is a new build system based on a new Python program instead of
535raw makefiles. Now wxPython builds are virtually the same on MSW or
536Unix systems. See the end of this file for new build instructions and
537see distrib/build.py for more details.
538
539wxDC.Bilt now includes the useMask parameter, and has been split into
540two different versions. wxDC.BlitXY is like what was there before and
541takes raw coordinants and sizes, and the new wxDC.Blit is for the new
542interface using wxPoints and a wxSize.
543
544
545
546
547
548What's new in 2.1b2
549--------------------
550
551Added the missing wxWindow.GetUpdateRegion() method.
552
553Made a new change in SWIG (update your patches everybody) that
554provides a fix for global shadow objects that get an exception in
555their __del__ when their extension module has already been deleted.
556It was only a 1 line change in .../SWIG/Modules/pycpp.cxx at about
557line 496 if you want to do it by hand.
558
559It is now possible to run through MainLoop more than once in any one
560process. The cleanup that used to happen as MainLoop completed (and
561prevented it from running again) has been delayed until the wxc module
562is being unloaded by Python.
563
564I fixed a bunch of stuff in the C++ version of wxGrid so it wouldn't
565make wxPython look bad.
566
567wxWindow.PopupMenu() now takes a wxPoint instead of x,y. Added
568wxWindow.PopupMenuXY to be consistent with some other methods.
569
570Added wxGrid.SetEditInPlace and wxGrid.GetEditInPlace.
571
572You can now provide your own app.MainLoop method. See
573wxPython/demo/demoMainLoop.py for an example and some explaination.
574
575Got the in-place-edit for the wxTreeCtrl fixed and added some demo
576code to show how to use it.
577
578Put the wxIcon constructor back in for GTK as it now has one that
579matches MSW's.
580
581Added wxGrid.GetCells
582
583Added wxSystemSettings static methods as functions with names like
584wxSystemSettings_GetSystemColour.
585
586Removed wxPyMenu since using menu callbacks have been depreciated in
587wxWindows. Use wxMenu and events instead.
588
589Added alternate wxBitmap constructor (for MSW only) as
590 wxBitmapFromData(data, type, width, height, depth = 1)
591
592Added a helper function named wxPyTypeCast that can convert shadow
593objects of one type into shadow objects of another type. (Like doing
594a down-cast.) See the implementation in wx.py for some docs.
595
596Fixed wxImage GetData and SetData to properly use String objects for
597data transfer.
598
599Added access methods to wxGridEvent.
600
601New Makefile/Setup files supporting multiple dynamic extension modules
602for unix systems.
603
604Fixes for the wxGLCanvas demo to work around a strange bug in gtk.
605
606SWIG support routines now compiled separately instead of being bundled
607in wx.cpp.
608
609
610
611
612
613What's new in 2.1b1
614--------------------
615Fixed wxComboBox.SetSelection so that it actually sets the selected
616item. (Actually just removed it from wxPython and let it default to
617wxChoice.SetSelection which was already doing the right thing.)
618
619Added the Printing Framework.
620
621Switched back to using the wxWindows DLL for the pre-built Win32
622version. The problem was needing to reinitialize static class info
623data after loading each extension module.
624
625Lots of little tweaks and additions to reflect changes to various
626wxWindows classes.
627
628Fixed a bug with attaching objects to tree items. Actually was a
629symptom of a larger problem with not obtaining the interpreter lock
630when doing any Py_DECREFs.
631
632wxSizer and friends. Sizers are layout tools that manage a colection
633of windows and sizers. Different types of sizers apply different
634types of layout algorithms. You saw it here first! These classes are
635not even in the wxWindows C++ library yet!
636
637
638
639What's new in 2.0b9
640-------------------
641Bug fix for ListCtrl in test4.py (Was a missing file... DSM!)
642
643Bug fix for occassional GPF on Win32 systems upon termination of a
644wxPython application.
645
646Added wxListBox.GetSelections returning selections as a Tuple.
647
648Added a wxTreeItemData that is able to hold any Python object and be
649associated with items in a wxTreeCtrl. Added test pytree.py to show
650this feature off.
651
652Added wxSafeYield function.
653
654OpenGL Canvas can be optionally compiled in to wxPython.
655
656Awesome new Demo Framework for showing off wxPython and for learning
657how it all works.
658
659The pre-built Win32 version is no longer distributing the wxWindows
660DLL. It is statically linked with the wxWindows library instead.
661
662Added a couple missing items from the docs.
663
664Added wxImage, wxImageHandler, wxPNGHandler, wxJPEGHandler,
665wxGIFHandler and wxBMPHandler.
666
667Added new methods to wxTextCtrl.
668
669Fixed some problems with how SWIG was wrapping some wxTreeCtrl
670methods.
671
672
673
674What's new in 2.0b8
675-------------------
676Support for using Python threads in wxPython apps.
677
678Several missing methods from various classes.
679
680Various bug fixes.
681
682
683
684What's new in 2.0b7
685-------------------
686Added DLG_PNT and DLG_SZE convienience methods to wxWindow class.
687
688Added missing constructor and other methods for wxMenuItem.
689
690
691
692What's new in 2.0b6
693-------------------
694Just a quickie update to fix the self-installer to be compatible with
695Python 1.5.2b2's Registry settings.
696
697
698What's new in 2.0b5
699-------------------
700Well obviously the numbering scheme has changed. I did this to
701reflect the fact that this truly is the second major revision of
702wxPython, (well the third actually if you count the one I did for
703wxWindows 1.68 and then threw away...) and also that it is associated
704with the 2.0 version of wxWindows.
705
706I have finally started documenting wxPython. There are several pages
707in the wxWindows documentation tree specifically about wxPython, and I
708have added notes within the class references about where and how wxPython
709diverges from wxWindows.
710
711Added wxWindow_FromHWND(hWnd) for wxMSW to construct a wxWindow from a
712window handle. If you can get the window handle into the python code,
713it should just work... More news on this later.
714
715Added wxImageList, wxToolTip.
716
717Re-enabled wxConfig.DeleteAll() since it is reportedly fixed for the
718wxRegConfig class.
719
720As usual, some bug fixes, tweaks, etc.
721
722
723
724What's new in 0.5.3
725-------------------
726Added wxSashWindow, wxSashEvent, wxLayoutAlgorithm, etc.
727
728Various cleanup, tweaks, minor additions, etc. to maintain
729compatibility with the current wxWindows.
730
731
732
733What's new in 0.5.0
734-------------------
735Changed the import semantics from "from wxPython import *" to "from
736wxPython.wx import *" This is for people who are worried about
737namespace pollution, they can use "from wxPython import wx" and then
738prefix all the wxPython identifiers with "wx."
739
740Added wxTaskbarIcon for wxMSW.
741
742Made the events work for wxGrid.
743
744Added wxConfig.
745
746Added wxMiniFrame for wxGTK.
747
748Changed many of the args and return values that were pointers to gdi
749objects to references to reflect changes in the wxWindows API.
750
751Other assorted fixes and additions.
752
753
754
755
756What's new in 0.4.2
757-------------------
758
759wxPython on wxGTK works!!! Both dynamic and static on Linux and
760static on Solaris have been tested. Many thanks go to Harm
761<H.v.d.Heijden@phys.tue.nl> for his astute detective work on tracking
762down a nasty DECREF bug. Okay so I have to confess that it was just a
763DSM (Dumb Stupid Mistake) on my part but it was nasty none the less
764because the behavior was so different on different platforms.
765
766The dynamicly loaded module on Solaris is still segfaulting, so it
767must have been a different issue all along...
768
769
770
771What's New in 0.4
772-----------------
773
7741. Worked on wxGTK compatibility. It is partially working. On a
775Solaris/Sparc box wxPython is working but only when it is statically
776linked with the Python interpreter. When built as a dyamically loaded
777extension module, things start acting weirdly and it soon seg-faults.
778And on Linux both the statically linked and the dynamically linked
779version segfault shortly after starting up.
780
7812. Added Toolbar, StatusBar and SplitterWindow classes.
782
7833. Varioius bug fixes, enhancements, etc.
784
785----------------------------------------------------------------------