On 12/12/2007, Giuliano Colla <[EMAIL PROTECTED]> wrote: > If your thread performs a side task which takes data from your main > thread, and then processes them in parallel, then of course you don't > need to deal with GUI, other than for error messages, which can be > handled quite easily. But if your threads do receive data which must be > fed to the main thread, and which must trigger visual events, then you > become aware of the strong limitations of current implementation.
I'm no Threads expert, but have been studying code that uses threads heavily. A few such examples are the Borland Multi-Threading competition [1] that was held a few years back. There all the entries were GUI apps and the threads managed to update the GUI just fine (via Synchronized methods I believe). So is it really a issue, or am I not understanding the underlying problem? [1] - I can supply the URL if anybody is interested. Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
