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 wouldn't generally advocate showing new window objects from a non-
> main thread, but I think it might work on OSX in this case... Not
> sure what we could do about the win32 case though (or X / *nix
> either) so that might just introduce inconsistencies between platforms.
I think I'd considered that, but didn't like the idea for two reasons:
1) Puts a threading requirement on the app/fltk
2) I am not so sure OSX can have two event loops going on in
any stable way. Not sure about this, but sure didn't want
to take any chances with having single threaded apps suddenly
become multithreaded by using FNFC, and having the user
be unprepared for "threading issues".
3) Threads are evil ;)
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
