On Jun 29, 2011, at 8:29 AM, Jacek Kałucki wrote:
> It's because wx.CallAfter doesn't guarantee execution order to be retained.
That was something I talked with Robin Dunn about years ago, and he
said that while the order isn't guaranteed, in his tests it almost always was
correct. The only other option would be to add a Queue structure into the event
loop, and while that would ensure correct ordering, it would complicate the
code considerably.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
