> For example, in a worker thread, I would advocate always calling > Fl::awake(); just before calling unlock, to make sure that the main fltk > thread was notified to deal with your changes as soon as possible, that > sort of thing.
Thanks Ian. I got the sense that Fl::awake(...) is used specifically to send a *message* to the application's main thread, and that application logic (rather than FLTK code) was meant to act on that message. In my case, where Fl::run() (rather than application code) is executing on the main thread, is it still okay for me to Fl::awake()? And if so, what argument(s) should I provide to Fl::awake()? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
