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