On 11/19/06, Al Boldi <[EMAIL PROTECTED]> wrote:
Great, but is it thread-safe?
No major GUI toolkit is really thread-safe! Please remember that fpGUI is still under heavy development, but at it's first release it will be as thread-safe as we can make it! I use threads wherever it makes sense in my work, and as I am planning on using fpGUI for work purposes, thread-safe is a requirement for me. Food for thought. A quote from the Internet, which I tend to agree with... ------------------------ No major GUI toolkit is really thread-safe -- Thu, 08 Apr 2004 06:08:10 -0700 Most toolkits are not thread-safe for upper-level GUI functions. For example, you cannot do GUI operations in OS X's Cocoa API from multiple threads. The recommended model by Apple is to spawn "worker" threads that send messages to the single GUI thread, or do things like setNeedsDisplay: on windows to tell the GUI thread to redraw them. While I'm definitely not an expert on GDI/GDI+ programming, I'm fairly sure its not significantly thread-safe for GUI operations either. KDE/Qt also have some serious multi-thread issues for higher-level GUI classes. In general, if you want to write a cross-platform GUI application, you cannot rely on a completely thread-safe API unless you use a toolkit directly on the framebuffer. ------------------------ -- Graeme Geldenhuys Location: S 34° 03.168' E018° 49.342' http://tinyurl.com/y6lc26 There's no place like 127.0.0.1 _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
