Hi all,
There's a 2.9.0.1 preview build available for everybody to play with. There are binaries for Mac and Windows, and a source tarball for everybody else. Take a look at the new build instructions, they're *lots* simpler than they used to be.
URL: http://wxpython.wxcommunity.com/preview/20100111/
Changes: http://wxpython.wxcommunity.com/preview/20100111/CHANGES.html
--
Robin Dunn
Software Craftsman
http://wxPython.org
Hi Robin,
2010/1/12 Robin Dunn:
Hi all,
There's a 2.9.0.1 preview build available for everybody to play with. There
are binaries for Mac and Windows, and a source tarball for everybody else.
Take a look at the new build instructions, they're *lots* simpler than they
used to be.URL: NameBright - Coming Soon
Changes: NameBright - Coming Soon
There are few issues with the pre-release, namely:
1) DataViewCtrl-related demos do not work:
Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wxPython2.9
Docs and Demos\demo\DVC_ListCtrl.py", line 3, in <module>
import wx.dataview as dv
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\dataview.py",
line 11, in <module>
import _dataview
ImportError: No module named _dataview
2) The same happens with PropertyGrid:
Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wxPython2.9
Docs and Demos\demo\PropertyGrid.py", line 6, in <module>
import wx.propgrid as wxpg
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\propgrid.py",
line 9, in <module>
import _propgrid
ImportError: No module named _propgrid
Possibly the _dataview.pyd and _propgrid.pyd have not been generated somehow.
3) The wx.ToolBook demo hangs without displaying anything, and needs
to be killed using the three-fingers salute;
4) The BitmapCombobox demo shows an "Unhandled exception" when
selecting any item in the combobox. Clicking on "Ignore" continues the
program flow normally;
5) The Validator demo - dialog example (and possibly other demos which
use wx.StdDialogButtonSizer) shows a funny alignment of "OK" and
"Cancel" buttons. It might be the platform default behaviour, but the
validator demo dialog looks really weird and out of place to me (see
also the ExpandoTextCtrl Set Max Height dialog);
6) The wx.ListBook partially hides the selected list item at startup
(i.e., at startup the first list item is selected but the list control
is scrolled down so that the first item is almost hidden);
7) I get an assertion error while running the SizedControls demo, and
specifically the first button "Sized Controls Form Dialog". A
screenshot of the error is attached to this e-mail;
8) The "Image.py" demo is missing an image. I get this error:
10:40:29: Error: Can't load image from file 'bitmaps\image.bmp': file
does not exist.
9) The GraphicsContext demo keeps drawing and re-drawing itself
forever until killed;
10) The PlateButton demo flickers like mad when selecting one platebutton;
10) AUI (meaning agw.aui) is broken: this might be due to the new
wx.BoxSizer implementation (although I haven't investigated yet). Is
there any way we might convince wx-devs to implement an old-style
wx.BoxSizer which will bring back the previous behaviour? Something
like wx.ProportionalBoxSizer or wx.OldBoxSizer, whatever. Otherwise I
will need to code one in Python, which will make AUI slower;
11) BalloonTip is broken: again, this may be due to the new sizers
implementation (not sure though);
12) ButtonPanel is broken: while starting the demo, I get an assertion
error regarding wx.StatusBar (attached image);
13) FaltMenu is broken: while hovering on the "Style" top menu I get a
hard crash of Python with the usual Windows message;
14) wx.RegionFromPoints is now expecting 2 inputs, although the second
one is always defaulted to fillStyle=wxODDEVEN_RULE (as per
documentation). I get this error:
Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\lib\agw\flatnotebook.py",
line 4572, in OnPaint
renderer.DrawTabs(self, dc)
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\lib\agw\flatnotebook.py",
line 3033, in DrawTabs
self.DrawTab(pc, dc, posx, i, tabWidth, tabHeight, pc._nTabXButtonStatus)
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\lib\agw\flatnotebook.py",
line 3114, in DrawTab
pc._pagesInfoVec[tabIdx].SetRegion(tabPoints)
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\lib\agw\flatnotebook.py",
line 1140, in SetRegion
self._region = wx.RegionFromPoints(points)
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\_gdi.py",
line 1706, in RegionFromPoints
val = _gdi_.new_RegionFromPoints(*args, **kwargs)
TypeError: new_RegionFromPoints() takes at least 2 arguments (1 given)
c:\python25\lib\site-packages\wx-2.9.0-msw-unicode\wx\_gdi.py(1706)RegionFromPoints()
-> val = _gdi_.new_RegionFromPoints(*args, **kwargs)
In FlatNotebook while attempting to use VC8 style tabs;
15) The GradientButton demo is broken, no image is shown on one of the
gradient buttons (but the image is there, so it may still be some
sizer quirk);
16) I get this error on the ToasterBox demo:
11:00:47: Error: Can't load image from file 'agw/bitmaps/sttfont.png':
file does not exist.
And the general layout of ToasterBox seems broken.
This is all on Windows XP SP2, Python 2.5.4.
I think this is it for the moment. I knew 2.9 was going to break some
parts of AGW but I wasn't expecting such a huge failure everywhere. In
any case, it's not your fault. Thank you for the pre-release and for
the hard work on wxPython!
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
Hi,
Windows 7, Python 2.6.4
I only downloaded the run time and tested, quite quickly, with
some of my applications. With these, I know the best what could raise
problems and I also should add, my applications (scientific stuff) are
mainly using core widgets.
A not "too-in-depth" report, knowing and keeping in mind that
wxPython 2.9 is not only a new release, but it represents
the convergence/unification of the previous ansi/unicode wxWidgets
builds.
wxPython 2.9 behaves as I expected with plus and minus.
+ : * Finally a real printpreview. I did not check numbers, but
it seems the preview canvas size does correspond to the
printer paper size. (I know it is wxWidgets stuff).
* Populating text widgets with strings, <str> or <unicode>,
is working smoothly. In previous *unicode* builds,
populating a text widget with something like u'abc需'
failed (notw these cp1252 chars).
- : * The stc
* wx.Grid
Installation
Prior to the wxPython 2.9.0 installation, my new box had only one
wxPython version, wx-2.8-msw-ansi, that means only on wx dir in
the ....\site-packages dir, ....\site-packages\wx-2.8-msw-ansi.
I installed wxPython 2.9 not letting the installer defining 2.9
as the default wxPython version and modified wx.pth by hand.
I can define the wx.pth the way I wish, it seems
"import wx" always pointed to wxPython 2.8.
It's only when I renamed wx-2.8-msw-ansi -> awx-2.8-msw-ansi that
it works. Strange! wx.pth, wx-2.9.0-msw-unicode, maps to the wx dir.
An
import wxversion
wxversion.select('2.9')
did not give problems.
Less technical
I suggest this wxPython should be named
wx-***-2.9.0-***-*** without any unicode mention.
- Obviously, there are no more ansi/unicode builds
- It may confuse an experimented user, thinking there
is still something else than unicode.
- It may confuse a beginner. Letting him to know this is
a unicode build does not make sense.
- As pointed before (strings), this new "unicode build"
is really different from the previous "unicode builds"
Last minute
It seems the wx.Grid is again suffering from its old
desease, the impossibility to enter text in a cell
if the text you wish to type does not start with
an ascii char.
Regards
Jean-Michel Fauth, Swizerland
Addendum.
Well, it seems google has his own interpretation of some bytes
sequences.
\* Populating text widgets with strings, <str> or <unicode>, is working smoothly\. In previous \*unicode\* builds, populating a text widget with something like u'abc需' failed \(notw these cp1252 chars\)\.
The unicode u'...' should be read * a b c é € œ *
ud.name(u'a')
LATIN SMALL LETTER A
ud.name(u'é')
LATIN SMALL LETTER E WITH ACUTE
ud.name(u'€')
EURO SIGN
ud.name(u'œ')
LATIN SMALL LIGATURE OE
Regards
Jean-Michel Fauth, Swizerland
Hi Robin,
There are few issues with the pre-release, namely:
Thanks for testing!
1) DataViewCtrl-related demos do not work:
Traceback (most recent call last):
[...]
import _dataview
ImportError: No module named _dataview2) The same happens with PropertyGrid:
Traceback (most recent call last):
[...]
import _propgrid
ImportError: No module named _propgridPossibly the _dataview.pyd and _propgrid.pyd have not been generated somehow.
Generated, but left out of the installer. Fixed.
3) The wx.ToolBook demo hangs without displaying anything, and needs
to be killed using the three-fingers salute;
It seems to be getting stuck in an endless EVT_SIZE recursion, but only on Windows. Weird... Found it, fixed it.
4) The BitmapCombobox demo shows an "Unhandled exception" when
selecting any item in the combobox. Clicking on "Ignore" continues the
program flow normally;
The widget is now native on Windows and GTK, so needed to fix the base class declaration in the wrapper files. Fixed.
5) The Validator demo - dialog example (and possibly other demos which
use wx.StdDialogButtonSizer) shows a funny alignment of "OK" and
"Cancel" buttons. It might be the platform default behaviour, but the
validator demo dialog looks really weird and out of place to me (see
also the ExpandoTextCtrl Set Max Height dialog);
Adding the button sizer to the main sizer with the expand flag takes care of it. Fixed.
6) The wx.ListBook partially hides the selected list item at startup
(i.e., at startup the first list item is selected but the list control
is scrolled down so that the first item is almost hidden);
Added a call to EnsureVisible. Fixed.
7) I get an assertion error while running the SizedControls demo, and
specifically the first button "Sized Controls Form Dialog". A
screenshot of the error is attached to this e-mail;
Some new sizer asserts that check if you are adding a growable row/col that is already growable. Seems a pretty stupid thing to worry about to me, but oh well. I added checks for Is[Col|Row]Growable to avoid it. Fixed.
8) The "Image.py" demo is missing an image. I get this error:
10:40:29: Error: Can't load image from file 'bitmaps\image.bmp': file
does not exist.
Another item left out of the windows installer. Fixed.
9) The GraphicsContext demo keeps drawing and re-drawing itself
forever until killed;
It does not do that here.
10) The PlateButton demo flickers like mad when selecting one platebutton;
It does not do that here, although I did discover a small glitch in the demo code (wrong method being called in the menu event).
10) AUI (meaning agw.aui) is broken: this might be due to the new
wx.BoxSizer implementation (although I haven't investigated yet). Is
there any way we might convince wx-devs to implement an old-style
wx.BoxSizer which will bring back the previous behaviour? Something
like wx.ProportionalBoxSizer or wx.OldBoxSizer, whatever. Otherwise I
will need to code one in Python, which will make AUI slower;
I'm not sure of the details, but there are some changes coming in 2.9.1 that are some sort of compromise between the two that seemed to make everybody happy.
11) BalloonTip is broken: again, this may be due to the new sizers
implementation (not sure though);12) ButtonPanel is broken: while starting the demo, I get an assertion
error regarding wx.StatusBar (attached image);
A bogus assert. Fixed.
13) FaltMenu is broken: while hovering on the "Style" top menu I get a
hard crash of Python with the usual Windows message;
I can't duplicate this. Perhaps one of my previous fixes has already taken care of this one too.
14) wx.RegionFromPoints is now expecting 2 inputs, although the second
one is always defaulted to fillStyle=wxODDEVEN_RULE (as per
documentation). I get this error:Traceback (most recent call last):
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\lib\agw\flatnotebook.py",
[...]
File "C:\Python25\Lib\site-packages\wx-2.9.0-msw-unicode\wx\_gdi.py",
line 1706, in RegionFromPoints
val = _gdi_.new_RegionFromPoints(*args, **kwargs)
TypeError: new_RegionFromPoints() takes at least 2 arguments (1 given)c:\python25\lib\site-packages\wx-2.9.0-msw-unicode\wx\_gdi.py(1706)RegionFromPoints()
-> val = _gdi_.new_RegionFromPoints(*args, **kwargs)
In FlatNotebook while attempting to use VC8 style tabs;
A change in parameter type caused the correct typemap to not be used. Fixed.
15) The GradientButton demo is broken, no image is shown on one of the
gradient buttons (but the image is there, so it may still be some
sizer quirk);
That sample looks the same as 2.8.10.1 for me.
16) I get this error on the ToasterBox demo:
11:00:47: Error: Can't load image from file 'agw/bitmaps/sttfont.png':
file does not exist.
This image is included in the demo installer. Perhaps it is a similar problem to the above, perhaps something is changing the current working directory so it can't find the relative pathname.
On 1/12/10 3:04 AM, Andrea Gavana wrote:
--
Robin Dunn
Software Craftsman
IIRC this fix was put in the trunk after the 2.9.0 branch was made, so it will probably be in 2.9.1.
On 1/12/10 7:55 AM, jmfauth wrote:
It seems the wx.Grid is again suffering from its old
desease, the impossibility to enter text in a cell
if the text you wish to type does not start with
an ascii char.
--
Robin Dunn
Software Craftsman
BTW...the alias for wx.Colour (wx.Color) seems to be missing. Is that
intentional?
Chris.
On Mon, 11 Jan 2010 22:41:58 -0800, Robin Dunn <robin@alldunn.com> wrote:
Hi all,
There's a 2.9.0.1 preview build available for everybody to play with.
There are binaries for Mac and Windows, and a source tarball for
everybody else. Take a look at the new build instructions, they're
*lots* simpler than they used to be.URL: NameBright - Coming Soon
Changes: NameBright - Coming Soon
Hi,
2010/1/14 Chris Spencer:
BTW...the alias for wx.Colour (wx.Color) seems to be missing. Is that
intentional?
I think (and I hope) it is intentional. It's about time we remove the
double-spelling in the API.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
One more oddity...
Where has the style property "wx.DIALOG_MODAL" gone?
One would think that this is an important style flag for creating
modal dialogs....
Chris.
Hi,
On Thu, Jan 14, 2010 at 4:45 PM, Andrea Gavana <andrea.gavana@gmail.com> wrote:
Hi,
2010/1/14 Chris Spencer:
BTW...the alias for wx.Colour (wx.Color) seems to be missing. Is that
intentional?I think (and I hope) it is intentional. It's about time we remove the
double-spelling in the API.
Yes this is intentional, remember some other conversation about it but
only found this one.
http://groups.google.com/group/wxPython-dev/browse_thread/thread/d83c9393b10112c5/804c6bfcd8c2e3ac
Cody Precord
Nevermind...I guess it's been removed.
Chris.
On Thu, 14 Jan 2010 18:13:09 -0500, Chris Spencer <cspencer@cinci.rr.com> wrote:
One more oddity...
Where has the style property "wx.DIALOG_MODAL" gone?
One would think that this is an important style flag for creating
modal dialogs....Chris.
Yes. I took a pass through the code a few months ago and axed everything was superfluous and was just in there due to poor decisions from the early days of wxPython. The wxColor alias was one of them.
On 1/14/10 2:41 PM, Chris Spencer wrote:
BTW...the alias for wx.Colour (wx.Color) seems to be missing. Is that
intentional?
--
Robin Dunn
Software Craftsman
Apparently it was never actually used in the wx code, so it was removed.
On 1/14/10 3:13 PM, Chris Spencer wrote:
One more oddity...
Where has the style property "wx.DIALOG_MODAL" gone?
One would think that this is an important style flag for creating
modal dialogs....
--
Robin Dunn
Software Craftsman
