I have both together in in a small application and it worked without a problem. Just be sure that you don't use the GUI directly from another thread. Use wxPostEvent instead.
-Matthias
···
Am Mon, 26 Sep 2005 10:33:56 +0200 hat Michele "O-Zone" Pinassi <liste@zerozone.it> geschrieben:
Hi all,
as far i know Twisted and Wx can co-operate well. I need to use that projects
in an app. under Windows and Linux.
The wxreactor works fairly well, but it’s a bit dodgy and heavy network activity can cause the GUI to appear unresponsive because both the network and GUI event loops are one and the same in this case.
Henning’s comment about the threadingreactor is about right. That allows network and GUI to go about thier business without undue conflict and is fairly safe. As said, be careful how you post events from the GUI to the network, and vice-versa. wx.CallAfter() is a simple means to add events to the wx event loop, and reactor.callLater() is a simple means to do so for the network side. NEVER directly reference between the two event loops and race conditions will at least be minimized.