On 11 Jun 2008, at 22:13, Greg Ercolano wrote: > imacarthur wrote: >> I wonder if it might be safe (on OSX) to spawn an child thread to >> hold the native file chooser, and allow the main thread to continue >> processing fltk events? >> > I think I'd considered that, but didn't like the idea for two > reasons: > > 1) Puts a threading requirement on the app/fltk
Although the presence of pthreads is a given on OSX, so we know the dependency can be met, and I wouldn't propose we do any fltk interactions between the threads. But it does start another thread the author might not expect... > 2) I am not so sure OSX can have two event loops going on in > any stable way. Yes, this one is tricky... Fortunately, from the other posts in the thread, it seems this question has gone away on its own, so we don't need to take the chance after all! > > 3) Threads are evil ;) And also the future. Octal core PC, anyone? Cheers Greg, -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
