Re: Re: About Creating New Packages/Widgets & Other Dev Help
Metallicow <[email protected]>
| Newsgroups | gmane.comp.python.wxpython.devel |
|---|---|
| Message-ID | <[email protected]> |
On Friday, February 7, 2014 at 3:08:06 PM UTC-6, Robin Dunn wrote: > > Metallicow wrote: > > SmartHighlighting Ex: if extra functionality is desired without > > overwriting the default handler. Im guessing event.Skip() should always > > be wisely placed somewhere in the event(beginning or end). > > It doesn't really matter where it is called. It just sets a flag that > is checked after the event handler returns. > > -- > Robin Dunn > Software Craftsman > http://wxPython.org Well... Yea. I now see that it DOES really matter where event.Skip() is placed, but only in instances where the code is doing *ALOT of stuff* and you want to choose specifically when to call the func. I noticed this in very in-depth tests with my ShapedBitmapButton. Like you said... normally this shouldn't matter much. ... But it does matter sometimes... ...especially in (recursive) loops and (recursive) event loops... ...urg... my head is spinning again... Thanks Robin. -- You received this message because you are subscribed to the Google Groups "wxPython-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.