Thread handling issue

[Tim Golden]

On 08/10/2011 11:51, Paul wrote:
> I think I'll wait for the user to actually make a change after cancelling the
> output selection, in case they go straight back without making changes. If they
> make a change I think I'll try what you suggested and send off a new thread, and
> send an event to the previous thread. Would this mean I'd need to use
> wx.lib.newevent.NewCommandEvent() to get a new event for each thread I create?
> and I'd have to pass the second return value from that, the event binder to the
> thread to bind to a clean up and exit method?

I'm afraid I'm more-or-less completely unfamiliar with the wx
way of doing things. You'd hopefully get useful answers from
a wx-focused mailing list. (This is always the difficulty in
translating between a "in theory you could do this" answer and
a real-world "I've got this and that and the other " situation :) )

TJG