Hello,
I just wanted to report a couple of things I noticed about the new
release. If it turns out that they're unknown bugs, I'll open bug reports
at SF.
Platform: slackware 9, gcc 3.2.2, GTK 2.2.1, wxPython 2.4.1.2 Unicode
(built from sources).
- according to the demo:
"""When unicode is enabled, then all functions and methods in wxPython
that return a wxString from the C++ function will return a Python
unicode object, and parameters to C++ functions/methods that expect a
wxString can accept either a Python string or unicode object. If a
string object is passed then it will be decoded into unicode using the
converter pointed to by wxConvCurrent, which will use the default
system encoding. [...]""" ^^^^^^^^^^^^^^^^^^^^
Well, this is not true. For GTK2, wxConvCurrent is always wxConvUTF8,
and this is annoying, because for example here (where I use ISO-8859-1),
every string that contains an accented letter fails to get encoded, and
is replaced by an empty string. I know I can solve the problem by
encoding the string myself, but this is not optimal. So I'd like to know
if the issue can be solved (and if not, the docs should be fixed IMHO)
- The demo crashes immediately if I try to drag the text in the
wxDragImage demo. This is the message I get:
"""
** (demo.py:4160): CRITICAL **: file pango-layout.c: line 266
(pango_layout_new): assertion `context != NULL' failed
** (demo.py:4160): CRITICAL **: file pango-layout.c: line 543
(pango_layout_set_font_description): assertion `layout != NULL' failed
** (demo.py:4160): CRITICAL **: file pango-layout.c: line 727
(pango_layout_set_text): assertion `layout != NULL' failed
** (demo.py:4160): CRITICAL **: file pango-layout.c: line 2002
(pango_layout_get_extents): assertion `layout != NULL' failed
(demo.py:4160): GLib-GObject-CRITICAL **: file gobject.c: line 1337
(g_object_unref): assertion `G_IS_OBJECT (object)' failed The program
'demo.py' received an X Window System error. This probably reflects a bug
in the program. The error was 'BadAlloc (insufficient resources for
operation)'. (Details: serial 15014 error_code 11 request_code 53
minor_code 0) (Note to programmers: normally, X errors are reported
asynchronously; that is, you will receive the error a while after
causing it. To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
"""
(But this is probably a wxWindows issue)
- It seems to me that DrawXXXList don't work as expected. With
2.4.0.6-GTK1.2, the "canvas" contents were updated "live", i.e. I could
see the various shapes getting painted. Now the "canvas" is frozen, and
painted all-at-once when all the shapes have been drawn.
- wxEditor: text selection doesn't work.
- Finally, not really a bug, and you may know it already, but...
wxStyledTextCtrl is so slow to be unusable (and I don't consider my
hardware too outdated - FWIW PIII 700 with 256Mb RAM and an 8Mb ATI-Rage
mobility card)
Hope this helps, and sorry if they have already been reported.
Cheers,
Alberto
