Antony Hodgson wrote:
On reflection, it seems reasonable to call Skip() to invoke the standard processing (ie, if the second page had static information, I wouldn't need my event handler). Not sure why it wouldn't require Skip() under GTK - that would seem to be incorrect behaviour. Anyone have any comments on this?
No it just means that wx port does not need to do any default behavior in that event handler in order to function correctly.
Matthew Scott wrote:
>
> I don't, however, yet know exactly when event.Skip() should be used and
> when it should not be used. Perhaps someone with this knowledge can add
> that to the wiki as well
The general rule of thumb is "if in doubt or something is not working correctly, then call Skip." 
Basically *not* calling event.Skip() will prevent the default functionality of the event from being performed (as well as the event handlers in parent classes or etc.) So the better question to ask is when to not call Skip(). There are many times when it doesn't matter either way, and so calling Skip won't hurt, but there are also times when you definitly don't want to call it. For example in a wx.EVT_KEY_DOWN handler not calling Skip will indicate that the raw key has been handled and so the system will not try to cook it into a EVT_CHAR event.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!