As you have to register to report bugs (anonymous bug reports are not
a bad thing :S) and this doesn't seem to have been reported yet, I
will write here instead. The wx.FindReplaceDialog is broken on
wxPython 2.9.3.1, at least with wxGTK on GNU/Linux with Python 2.7.2.
This is visible in the demo, whereby the text of the demo log
messages:
FIND -- Find text: asdf Replace text: Flags: 0
seen in the 2.8 versions is not shown (if I search for the text
'asdf'). Though I haven't tested extensively, it looks like that
wx.EVT_FIND event is not being generated (or at least I can't catch
it).
As you have to register to report bugs (anonymous bug reports are not
a bad thing :S)
Maybe not, but anonymous spam bots are a very bad thing. What is the problem with registering?
and this doesn't seem to have been reported yet, I
will write here instead. The wx.FindReplaceDialog is broken on
wxPython 2.9.3.1, at least with wxGTK on GNU/Linux with Python 2.7.2.
This is visible in the demo, whereby the text of the demo log
messages:
FIND -- Find text: asdf Replace text: Flags: 0
seen in the 2.8 versions is not shown (if I search for the text
'asdf'). Though I haven't tested extensively, it looks like that
wx.EVT_FIND event is not being generated (or at least I can't catch
it).
The events are not being sent to the parent of the dialog, but they are being sent to the dialog itself. This is actually more in line with how event propagation is supposed to work, so it would be hard to call this a bug. I've changed the demo to bind the event handlers to the find dialogs instead of the parent and it works as expected again.