Daniel wrote: > > And here I thought fltk was thread safe?
No, but i think accessing GUI from many threads is a bat habit anyway. Do whatever you want in your threads to process some data and inform your (main) GUI-responsible thread about the changes through some messages, flags etc. If you really need to change a GUI state from a child thread you can use Fl::lock(), but it is a pretty brutal one (locks more-less everything) so I would rather recommend the use of some messaging system. Roman _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
