>  Actually a surprisingly large number of GUI applications are 
> multithreaded,
> by necessity. Basically any GUI application which performs tasks which 
> take
> time to complete (be it because the task is very cpu-intensive and takes
> time to calculate, or because the program has to wait for something, eg.
> data to be downloaded from the internet) have to be multithreaded: One
> thread for the task and another for updating the GUI.

IIRC there are some API functions to poll for new data, ie check if any 
bytes have been received.  If you do this at regular intervals then you can 
create a single-threaded application that is still responsive as usual to 
GUI events.

Post a reply to this message