Announcing
----------
I'm pleased to announce the 2.6.0.0 release of wxPython, now available
for download at http://wxpython.org/download.php. This release
consists of one more round of stabalization work (bug fixes and such)
since the 2.5 series, and a few minor new features. This first 2.6
release marks the begining of a new stable release series, which for
Python means that there will be no API compatibility breakage for the
life of the series. (It means more than that for the core C++ code,
see http://wiki.wxpython.org/index.cgi/ReleaseSeries) See the changes
list below for details.
What is wxPython?
-----------------
wxPython is a GUI toolkit for the Python programming language. It
allows Python programmers to create programs with a robust, highly
functional graphical user interface, simply and easily. It is
implemented as a Python extension module that wraps the GUI components
of the popular wxWidgets cross platform library, which is written in
C++.
wxPython is a cross-platform toolkit. This means that the same program
will usually run on multiple platforms without modifications.
Currently supported platforms are 32-bit Microsoft Windows, most Linux
or other Unix-like systems using GTK or GTK2, and Mac OS X.
Changes in 2.6.0.0
------------------
wxMSW: Fixed wx.TransientPopupWindow (and therefore wx.TipWindow) to
auto-dismiss when the mouse is clicked outside of the popup like it is
supposed to.
wxMSW: Fixed bug #1167891 wx.Notebook display problem with wx.NB_MULTILINE.
wxMSW: Fixed bad cliping of hidden windows inside of wx.StaticBox.
wxGTK: The configure flags for selecting GTK+ 1.2.x or 2.x has
changed slightly. It is now --with-gtk[=VERSION] where VERSION is
either '1', '2' or 'any'. The default is '2'.
wx.stc.StyledTextCtrl: Added the following methods for alternate ways
to set and fetch text from the document buffer. They work similarly
to the existing methods of the same name, except that they don't go
through the same string/unicode <--> wxString conversions. The "Raw"
methods will do no conversions at all and in a unicode build of
wxPython the strings will be in the utf-8 encoding and in an ansi
build no assumption is made about the encoding. The "UTF8" functions
will attempt to always get/set utf-8 text, which it will always be
able to do in a unicode build, and in an ansi build it will depend on
the content of the utf-8 used being compatible with the current
encoding, (you'll get an exception otherwise.)
=================== ====================
AddTextRaw AddTextUTF8
InsertTextRaw InsertTextUTF8
GetCurLineRaw GetCurLineUTF8
GetLineRaw GetLineUTF8
GetSelectedTextRaw GetSelectedTextUTF8
GetTextRangeRaw GetTextRangeUTF8
SetTextRaw SetTextUTF8
GetTextRaw GetTextUTF8
AppendTextRaw AppendTextUTF8
=================== ====================
wx.stc.StyledTextCtrl: Added the StyleSetFontEncoding(style, enc)
method that allows you to set the encoding to be used by the font for
a particular style.
wxMac: Fixed wx.ComboBox to forward the EVT_CHAR, EVT_KEY_DOWN,
EVT_KEY_UP and EVT_TEXT events from its embedded text control.
wxMac: Corrected refresh bugs in wxGrid.
XRCed: Updated to version 0.1.5.
* Added wxWizard, wxWizardPageSimple (only from pull-down menu).
* Hide command for test window.
* Replacing classes works better.
* Added Locate tool.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
--
http://mail.python.org/mailman/listinfo/python-list
