Just to to hunt what is wrong, I tried out with Python2.3 and Python2.4
on one hand, and with ansi and unicode version of wxPython on the other
hand. Which is interesting and weird is that this bug only happens with
all unicode versions of wxPython, not with the ansi versions! So I
think I’ll report this as a bug, unless somebody with unicode (on
Windows), can not reproduce this bug. For me as a daily user of SPE
myself, it is even worth to drop unicode (but I strongly regret it) and
for now it will be the only solution I can recommend to SPE users.
Now I understand the confusion, as I worked before with the ansi
versions, I never had this bug. When I switched to wxPython 2.6.1.0, I
choose for unicode. Like that it looked it was version related, but now
it is clear it is unicode related.
What would be now the most recommend way to post this bug? Is anybody
taking care of wxPython at the moment?
Is there any chance of new releases of wxPython in Robin’s absense? Is
it possible to have a new unofficial build at
? But this is
probably another, more general question.
Stani
(next release planned for next week)
···
http://starship.python.net/crew/robind/wxPython/daily/
http://pythonide.stani.be
http://pythonide.stani.be/screenshots
Date: Fri, 19 Aug 2005 19:44:31 +0200
To: From: Subject: RE: [wxPython-users] Re: Find Dialog bug in wxPython 2.6.1.0?!
Message-ID:
I must click twice on my machine, also in the demo:
WinXP Pro
Python 2.3.2
wxPython 2.6.1.0 unicode (and several previous versions)
Works on first go for me in the demo:
WinXP Pro
Python 2.4.1
wxPython 2.6.1.0 (ansi)
So it depends on the Python version?? Or some Windows preference?
Sorry, I can't switch my Python version just now.
Best regards,
Henning Hraban Ramm
S=FCdkurier Medienhaus / MediaPro
Support/Admin/Development Dept.
wxPython-users@lists.wxwidgets.orgHenning.Ramm@mediapro-gmbh.deF92274058556DE42B94B148EEFB91839021CB531@exchange-03.suedkurier.de>>>>>>>>>>>>
What do you mean “…in Robin’s absense”? Is the xwPython author/maintainer qutting the project?
···
On 8/19/05, SPE - Stani’s Python Editor < spe.stani.be@gmail.com> wrote:
Just to to hunt what is wrong, I tried out with Python2.3 and Python2.4
on one hand, and with ansi and unicode version of wxPython on the other
hand. Which is interesting and weird is that this bug only happens with
all unicode versions of wxPython, not with the ansi versions! So I
think I’ll report this as a bug, unless somebody with unicode (on
Windows), can not reproduce this bug. For me as a daily user of SPE
myself, it is even worth to drop unicode (but I strongly regret it) and
for now it will be the only solution I can recommend to SPE users.
Now I understand the confusion, as I worked before with the ansi
versions, I never had this bug. When I switched to wxPython 2.6.1.0, I
choose for unicode. Like that it looked it was version related, but now
it is clear it is unicode related.
What would be now the most recommend way to post this bug? Is anybody
taking care of wxPython at the moment?
Is there any chance of new releases of wxPython in Robin’s absense? Is
it possible to have a new unofficial build at
http://starship.python.net/crew/robind/wxPython/daily/? But this is
probably another, more general question.
Stani
http://pythonide.stani.be (next release planned for next week)
http://pythonide.stani.be/screenshots
Date: Fri, 19 Aug 2005 19:44:31 +0200
To: <wxPython-users@lists.wxwidgets.org>
From: <Henning.Ramm@mediapro-gmbh.de>
Subject: RE: [wxPython-users] Re: Find Dialog bug in wxPython [2.6.1.0](http://2.6.1.0)?!
Message-ID:
<F92274058556DE42B94B148EEFB91839021CB531@exchange-03.suedkurier.de>
>>I must click twice on my machine, also in the demo:
>>WinXP Pro
>>Python 2.3.2
>>wxPython [
2.6.1.0](http://2.6.1.0) unicode (and several previous versions)
>Works on first go for me in the demo:
>WinXP Pro
>Python 2.4.1
>wxPython [
2.6.1.0](http://2.6.1.0) (ansi)
So it depends on the Python version?? Or some Windows preference?
Sorry, I can't switch my Python version just now.
Best regards,
Henning Hraban Ramm
S=FCdkurier Medienhaus / MediaPro
Support/Admin/Development Dept.
I think it's a wxWidgets bug.
Try to put a MessageDialog in the find and find next event handler and
see if the behaviour is the same.
Ricardo
···
On Fri, 2005-08-19 at 23:01 +0200, SPE - Stani's Python Editor wrote:
Just to to hunt what is wrong, I tried out with Python2.3 and
Python2.4 on one hand, and with ansi and unicode version of wxPython
on the other hand. Which is interesting and weird is that this bug
only happens with all unicode versions of wxPython, not with the ansi
versions! So I think I'll report this as a bug, unless somebody with
unicode (on Windows), can not reproduce this bug. For me as a daily
user of SPE myself, it is even worth to drop unicode (but I strongly
regret it) and for now it will be the only solution I can recommend to
SPE users.
Now I understand the confusion, as I worked before with the ansi
versions, I never had this bug. When I switched to wxPython 2.6.1.0, I
choose for unicode. Like that it looked it was version related, but
now it is clear it is unicode related.
What would be now the most recommend way to post this bug? Is anybody
taking care of wxPython at the moment?
No, but he's been busy with personal stuff, and will be for a while.
He announced it recently on the list.
···
On 8/19/05, Ryan McDonald <mcdonald.ryan@gmail.com> wrote:
What do you mean "...in Robin's absense"? Is the xwPython author/maintainer
qutting the project?
--
Bill Woodward wpwood@saifa.net http://www.saifa.net
"I have more trouble with D. L. Moody than with any other man I ever
met." -- D. L. Moody
s/D. L. Moody/Bill Woodward/g
I confirm that is a bug in wxWidgets.
I already sent the following message to wx-dev:
"
I want someone confirm the following FindReplaceDialog misbehavior.
When I first click on Find the event handler is executed but then
I must click twice on button Find to do a find next.
This happens on WinXP but not on Windows98.
I'm using the latest wxPython. But I test with the wxWidgets dialogs
sample too, and the behavior is the same.
With the wxWidgets dialogs sample it happens only when I compile
with wxUSE_UNICODE_MSLU=1 and cut off the wxMessageDialog from the
find event handler.
"
Maybe it's better to wait for a response, if we don't get one, it will
be better to fill a bug report.
Ricardo
···
On Fri, 2005-08-19 at 23:21 +0100, Ricardo Pedroso wrote:
On Fri, 2005-08-19 at 23:01 +0200, SPE - Stani's Python Editor wrote:
> Just to to hunt what is wrong, I tried out with Python2.3 and
> Python2.4 on one hand, and with ansi and unicode version of wxPython
> on the other hand. Which is interesting and weird is that this bug
> only happens with all unicode versions of wxPython, not with the ansi
> versions! So I think I'll report this as a bug, unless somebody with
> unicode (on Windows), can not reproduce this bug. For me as a daily
> user of SPE myself, it is even worth to drop unicode (but I strongly
> regret it) and for now it will be the only solution I can recommend to
> SPE users.
>
> Now I understand the confusion, as I worked before with the ansi
> versions, I never had this bug. When I switched to wxPython 2.6.1.0, I
> choose for unicode. Like that it looked it was version related, but
> now it is clear it is unicode related.
>
> What would be now the most recommend way to post this bug? Is anybody
> taking care of wxPython at the moment?
I think it's a wxWidgets bug.
Try to put a MessageDialog in the find and find next event handler and
see if the behaviour is the same.
Ricardo