I previously reported this as a problem/issue with the
CustomTreeControl, but on further investigation, the issue is really
with the "expandoTextControl", which is used to edit the labels of the
custom trees.
Attached is a small runnable sample of that demonstrates the problem.
Enter some text in the second text control, the press the "update"
button. The value from the second field should be displayed in the
first.
This problem seems to be isolated builds greater than 2.8.8.0-ansi as
this test works fine on these later version. When entering the text
and pressing the update button, it appears that the first controls
values are displayed as the ascii representation of unicode
characters.
Note that using a wx-unicode build does not present this
problem/issue, however, our applications is based on the ansi build,
so switching to the unicode build now presents its own challenges.
I previously reported this as a problem/issue with the
CustomTreeControl, but on further investigation, the issue is really
with the "expandoTextControl", which is used to edit the labels of the
custom trees.
Attached is a small runnable sample of that demonstrates the problem.
Enter some text in the second text control, the press the "update"
button. The value from the second field should be displayed in the
first.
This problem seems to be isolated builds greater than 2.8.8.0-ansi as
this test works fine on these later version. When entering the text
and pressing the update button, it appears that the first controls
values are displayed as the ascii representation of unicode
characters.
Note that using a wx-unicode build does not present this
problem/issue, however, our applications is based on the ansi build,
so switching to the unicode build now presents its own challenges.
Any help/assistance would be appreciated.
Which platform? What is the default encoding for your locale? (import locale; print locale.getdefaultlocale() )
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Was anyone able to recreate this ?
Or any suggestions on how to work around ?
- currently we just kept our release at wx2.8.8.0
I use the unicode version of 2.8.9.1 on Windows XP, so this works just fine for me. I started with the ansi build for my first few months of wxPython programming and then switched to the unicode build. I don't recall having any trouble doing that. What kinds of issues are you having in converting to it?