I am using the wxSearchCtrl in one of my apps and have noticed some behavior on different platforms that I am hoping some light can be shed on.
Case 1: EVT_KEY_UP
In order to provide "as you type" live searching I have made a subclass of wxSearchCtrl and added an EVT_KEY_UP handler to it. This works on WXMAC and WXGTK but on on WXMSW.
Case 2: EVT_CHAR
In another subclass of wxSearchCtrl I am using a validator only allow integer input. The validator uses EVT_CHAR to capture input. This works on WXMAC, but not on WXGTK or WXMSW.
If I replace the wxSearchCtrl's with wxTextCtrl's then all events are fired as expected on all systems. From what I have read on the docs for the wxSearchCtrl on GTK and MSW is a generic control that is made in part from a wxTextCtrl, so I would expect the events to behave in a similar if not identical manner.
I would like to know if these are cases of "Not implemented yet", "Bug", or "User Error". Attached is an small example that can be used to test this. Run it from a terminal to see the messages print by the event handlers.
searchctrl_test.py (3.67 KB)