Re: [Pythoncard-users] please report wxPython 2.6.x issues

[Kevin A. <al...@se...>]

On the wxPython-dev list it was suggested that using

wx.SystemOptions.SetOptionInt("mac.textcontrol-use-mlte", 0)

might fix the problem if I read the description of current Mac wxPython 
2.6 behavior correctly. Also, it sounded like Robin might make this the 
default in the next 2.6 build. I'll try this out after OSCON, but I'm 
back on 2.5.x for this week.

ka
On Jul 30, 2005, at 5:05 PM, bra...@om... wrote:

>
> Kevin Altis wrote on 07/26/2005 01:36:01 PM:
>
>  > If you're using wxPython 2.6.x with the current release version of
>  > PythonCard or the version in cvs, please report any issues here. In
>  > particular, I would like to hear about differences from 2.5.x that
>  > you've had to workaround or that are simply broken and we need to
>  > address in the next release.
>
> The biggest problem I've noticed on the Mac (10.3/10.4) between 
> wxPython 2.5.3 and
>  2.6 is that sometimes TextField don't populate correctly on 2.6. They 
> appear
>  not to populate at all, but if you click in the field and drag left, 
> the
>  text will scroll into view. This problem doesn't happen on wxPython 
> 2.5.3.
>
> Note that these fields were created on Resource Editor running under 
> Windows.
> I'm not sure if that matters, but I notice there are some sizing 
> differences
> between the two platforms. It's almost as if the text is trying to 
> display
> on a field of a different size.
>
> This is the main reason I haven't upgraded any of our Mac users to
> Python 2.6 -- my PythonCard app doesn't have this problem under 
> wxPython2.5.3.