Quoth Paul Rubin <http://[EMAIL PROTECTED]>: | Christopher Subich <[EMAIL PROTECTED]> writes: | > > In the particular case of wxWidgets, it turns out that the *GUI* | > > blocks for long periods of time, preventing the *network* from | > > getting attention. But I agree with your position for other | > > toolkits, such as Gtk, Qt, or Tk. | > | > Wow, I'm not familiar with wxWidgets; how's that work? | | Huh? It's pretty normal, the gui blocks while waiting for events | from the window system. I expect that Qt and Tk work the same way.
In fact anything works that way, that being the nature of I/O. But usually there's a way to add your own I/O source to be dispatched along with the UI events -- the toolkit will for example use select() to wait for X11 socket I/O, so it can also respond to incoming data on another socket, provided along with a callback function by the application. Am I hearing that wxWindows or other popular toolkits don't provide any such feature, and need multiple threads for this reason? Donn Cave, [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list