[wxPython-users] calling wx.CallAfter after wx.Frame.Destroy

[Robin Dunn]

Aaron Brady wrote:
> However, if you block on MyCallAfterFunction's turn in the event queue, a
> previously posted and sunk event, which blocks on the same synchronization
> object, halts the queue, deadlocking it.

Well, yes.  However you could have that problem regardless of whether 
the frame is being destroyed or not, or if MainLoop is exiting.

Patient: "Doctor, my arm hurts when I move it like this, what should I do?"
Doctor: "Don't move your arm like that."

;-)

-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!