From the wxWidgets' book, there are some descriptions about the "Skip()" function:
For example, it is possible to filter out selected keystroke events sent by the system to a native text control by overriding wxTextCtrl and defining a handler for key events using EVT_KEY_DOWN. This would indeed prevent any key events from being sent to the native control, which might not be what is desired. In this case, the event handler function has to call wxEvent::Skip to indicate that the search for the event handler should continue.
To summarize, instead of explicitly calling the base class version, as you would have done with C++ virtual functions, you should instead call Skip on the event object.
For example, to make the derived text control only accept "a" to "z" and "A" to "Z," we would use this code:
void MyTextCtrl::OnChar(wxKeyEvent& event)
{
if ( wxIsalpha( event.KeyCode() ) )
{
// Keycode is within range, so do normal processing.
event.Skip();
}
else
{
// Illegal keystroke. We don't call event.Skip() so the
// event is not processed anywhere else.
wxBell();
}
}
So, the Skip() function can let the event propagate from derived class to bass class.
But for our usage in a C::B event handler, does Skip() go with the same mechanism? (From a derived class to cbPlugin class?)
Am I right?