Ron Griswold wrote:
I think you're right. Afterall, the expected behavior of the control
(for me anyway) is that it would work the same on all platforms,
otherwise you introduce a platform dependent behavior into a platform
independent toolkit. That said, I hadn't heard of wxYield before you
mentioned it so I have no idea what the implications of putting it into
the wx code might be.
Basically it runs the event loop until there are no more pending events and then it returns. The downside is that you may get events dispatched to other parts of your app that you are not expecting to receive, for example, a button click that invokes the same handler that called the wx.Yield...
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!