Matthias Melcher wrote: > FLTK *does* support multithreading through locks and awake signals, > but there is always only one single GUI thread (which additionally > must be the main thread of the application - a requirement by one of > the underlaying platforms).
Actually, I *think* this was originally a requirement forced on us by several of the underlying platforms - but I also think that there has been work by the OS/display driver folk along the way to try and remove this constraint. However, from fltk's point of view, running the GUI from the main thread still makes the most sense anyway... and means your code will work on any host, regardless of which particular variant of that system you find your code deployed onto! _______________________________________________ fltk mailing list fltk@easysw.com http://lists.easysw.com/mailman/listinfo/fltk
